CVE-2026-18620

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in Data Science Pipelines. A restricted user, or tenant, can exploit an improper authorization vulnerability in the setDefaultServiceAccount function. By specifying a more privileged ServiceAccount (SA) during a CreateRun request, an attacker can bypass authorization checks. This allows the tenant to run their containers with elevated privileges, potentially leading to the disclosure of sensitive information (secrets) and the ability to execute commands within other users' pods.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

August 10, 2026

Last Modified

September 8, 2026

Advisory Details (2)

Auto-updated Aug 10, 2026
Patch available. Sources: redhat.
redhat

2510320 – (CVE-2026-18620) CVE-2026-18620 data-sciences-pipeline: User-controlled ServiceAccount for workflow pods without authorization check — confused deputy

https://bugzilla.redhat.com/show_bug.cgi?id=2510320
redhat Patch Available

CVE-2026-18620 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-18620

Vendor Advisories for CVE-2026-18620(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-ml-pipelines-api-server-v2-rhel9:17882567112026-09-08redhat
redhatrhoai/odh-ml-pipelines-api-server-v2-rhel9:17871734172026-08-27redhat
redhatrhoai/odh-ml-pipelines-api-server-v2-rhel9:17851879202026-08-11redhat
redhatrhoai/odh-ml-pipelines-api-server-v2-rhel9:17851899342026-08-11redhat
redhatrhoai/odh-ml-pipelines-api-server-v2-rhel9:17849249512026-08-11redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 37× in last 7d / 164× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 237 total refreshes for this CVE.

  1. 2026-09-19 00:37 UTCEG score recompute
  2. 2026-09-19 00:37 UTCVendor advisory
  3. 2026-09-19 00:36 UTCGHSA enrichment
  4. 2026-09-18 19:27 UTCEPSS rescore
  5. 2026-09-18 13:09 UTCVendor advisory
  6. 2026-09-18 13:09 UTCGHSA enrichment
  7. 2026-09-18 01:34 UTCEG score recompute
  8. 2026-09-18 01:34 UTCVendor advisory
  9. 2026-09-18 01:34 UTCGHSA enrichment
  10. 2026-09-17 14:06 UTCVendor advisory
  11. 2026-09-17 14:06 UTCGHSA enrichment
  12. 2026-09-17 00:40 UTCEG score recompute
  13. 2026-09-17 00:40 UTCVendor advisory
  14. 2026-09-17 00:40 UTCGHSA enrichment
  15. 2026-09-16 14:07 UTCEPSS rescore
  16. 2026-09-16 05:14 UTCEPSS rescore
  17. 2026-09-16 02:23 UTCVendor advisory
  18. 2026-09-16 02:23 UTCGHSA enrichment
  19. 2026-09-15 13:41 UTCEG score recompute
  20. 2026-09-15 13:41 UTCVendor advisory
  21. 2026-09-15 13:41 UTCGHSA enrichment
  22. 2026-09-14 22:51 UTCVendor advisory
  23. 2026-09-14 22:51 UTCGHSA enrichment
  24. 2026-09-14 10:52 UTCVendor advisory
  25. 2026-09-14 10:52 UTCGHSA enrichment
Show 75 more
  1. 2026-09-13 23:25 UTCEG score recompute
  2. 2026-09-13 23:25 UTCVendor advisory
  3. 2026-09-13 23:25 UTCGHSA enrichment
  4. 2026-09-13 16:46 UTCEPSS rescore
  5. 2026-09-13 11:58 UTCVendor advisory
  6. 2026-09-13 11:58 UTCGHSA enrichment
  7. 2026-09-13 00:30 UTCEG score recompute
  8. 2026-09-13 00:30 UTCVendor advisory
  9. 2026-09-13 00:30 UTCGHSA enrichment
  10. 2026-09-12 15:00 UTCEPSS rescore
  11. 2026-09-12 13:02 UTCVendor advisory
  12. 2026-09-12 13:02 UTCGHSA enrichment
  13. 2026-09-12 01:35 UTCEG score recompute
  14. 2026-09-12 01:35 UTCVendor advisory
  15. 2026-09-12 01:35 UTCGHSA enrichment
  16. 2026-09-11 14:52 UTCEPSS rescore
  17. 2026-09-11 14:07 UTCEG score recompute
  18. 2026-09-11 14:07 UTCVendor advisory
  19. 2026-09-11 14:07 UTCGHSA enrichment
  20. 2026-09-11 09:36 UTCEPSS rescore
  21. 2026-09-11 01:00 UTCVendor advisory
  22. 2026-09-11 01:00 UTCGHSA enrichment
  23. 2026-09-10 13:26 UTCEG score recompute
  24. 2026-09-10 13:26 UTCVendor advisory
  25. 2026-09-10 13:26 UTCGHSA enrichment
  26. 2026-09-10 09:34 UTCEPSS rescore
  27. 2026-09-10 01:58 UTCEG score recompute
  28. 2026-09-10 01:58 UTCVendor advisory
  29. 2026-09-10 01:58 UTCGHSA enrichment
  30. 2026-09-09 10:48 UTCVendor advisory
  31. 2026-09-09 10:48 UTCGHSA enrichment
  32. 2026-09-08 23:21 UTCEG score recompute
  33. 2026-09-08 23:21 UTCVendor advisory
  34. 2026-09-08 23:20 UTCGHSA enrichment
  35. 2026-09-08 22:48 UTCEG score recompute
  36. 2026-09-08 22:48 UTCVendor advisory
  37. 2026-09-08 22:48 UTCGHSA enrichment
  38. 2026-09-08 22:00 UTCEPSS rescore
  39. 2026-09-08 04:39 UTCVendor advisory
  40. 2026-09-08 04:39 UTCGHSA enrichment
  41. 2026-09-07 17:11 UTCEG score recompute
  42. 2026-09-07 17:11 UTCVendor advisory
  43. 2026-09-07 17:11 UTCGHSA enrichment
  44. 2026-09-07 16:01 UTCEPSS rescore
  45. 2026-09-06 13:47 UTCEPSS rescore
  46. 2026-09-06 12:55 UTCVendor advisory
  47. 2026-09-06 12:54 UTCGHSA enrichment
  48. 2026-09-06 01:26 UTCEG score recompute
  49. 2026-09-06 01:26 UTCVendor advisory
  50. 2026-09-06 01:26 UTCGHSA enrichment
  51. 2026-09-05 13:23 UTCVendor advisory
  52. 2026-09-05 13:23 UTCGHSA enrichment
  53. 2026-09-05 01:50 UTCEG score recompute
  54. 2026-09-05 01:50 UTCVendor advisory
  55. 2026-09-05 01:50 UTCGHSA enrichment
  56. 2026-09-04 08:20 UTCEG score recompute
  57. 2026-09-04 08:20 UTCVendor advisory
  58. 2026-09-04 08:20 UTCGHSA enrichment
  59. 2026-09-04 05:06 UTCEPSS rescore
  60. 2026-09-03 16:37 UTCVendor advisory
  61. 2026-09-03 16:37 UTCGHSA enrichment
  62. 2026-09-03 01:59 UTCEG score recompute
  63. 2026-09-03 01:59 UTCVendor advisory
  64. 2026-09-03 01:59 UTCGHSA enrichment
  65. 2026-09-02 14:11 UTCEPSS rescore
  66. 2026-09-02 00:58 UTCEG score recompute
  67. 2026-09-02 00:58 UTCVendor advisory
  68. 2026-09-02 00:58 UTCGHSA enrichment
  69. 2026-09-01 13:53 UTCEPSS rescore
  70. 2026-09-01 13:31 UTCEG score recompute
  71. 2026-09-01 13:31 UTCVendor advisory
  72. 2026-09-01 13:31 UTCGHSA enrichment
  73. 2026-09-01 04:39 UTCEPSS rescore
  74. 2026-08-31 22:04 UTCVendor advisory
  75. 2026-08-31 22:04 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-18620?
CVE-2026-18620 is a high vulnerability published on August 10, 2026. A flaw was found in Data Science Pipelines. A restricted user, or tenant, can exploit an improper authorization vulnerability in the setDefaultServiceAccount function. By specifying a more privileged ServiceAccount (SA) during a CreateRun request, an attacker can bypass authorization checks. This…
When was CVE-2026-18620 disclosed?
CVE-2026-18620 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18620 actively exploited?
CVE-2026-18620 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.7% of all scored CVEs.
What is the CVSS score of CVE-2026-18620?
CVE-2026-18620 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-18620?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18620, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-18620

Explore →

Is Your Infrastructure Affected by CVE-2026-18620?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs