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.5%CVSS: 7.1Exploit: None knownExposed services: Not assessed

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.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 10, 2026

Last Modified

September 21, 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(7)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / 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-latency-predictor-training-rhel9:17865522502026-08-26redhat
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 30× in last 7d / 149× 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 309 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 on August 10, 2026, with the most recent update on September 21, 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.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18620?
CVE-2026-18620 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18620?
A fix for CVE-2026-18620 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-18620 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs