CVE-2026-18617

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

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

A fix is available — apply it.

A flaw was found in the Data Science Pipelines Operator (DSPO). A namespace editor can exploit a vulnerability in the spec.database.customExtraParams field, which allows for the injection of dangerous parameters into the MySQL Data Source Name (DSN) string. By manipulating these parameters, an attacker can enable LOCAL INFILE functionality and exfiltrate sensitive files, such as the service account token, from the operator pod. This can lead to privilege escalation, allowing a namespace editor to gain cluster-admin privileges.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 14, 2026

Advisory Details (2)

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

2510304 – (CVE-2026-18617) CVE-2026-18617 data-science-pipelines-operator: DSPO: MySQL DSN parameter injection via CustomExtraParams enables LOCAL INFILE file exfiltration from operator pod

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

CVE-2026-18617 - 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-18617

Vendor Advisories for CVE-2026-18617(4)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-data-science-pipelines-operator-controller-rhel9:17851879362026-08-11redhat
redhatrhoai/odh-data-science-pipelines-operator-controller-rhel9:17851893322026-08-11redhat
redhatrhoai/odh-data-science-pipelines-operator-controller-rhel9:17848334282026-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 / 71× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 21:00 UTCVendor advisory
  3. 2026-08-20 20:59 UTCGHSA enrichment
  4. 2026-08-20 07:51 UTCVendor advisory
  5. 2026-08-20 07:51 UTCGHSA enrichment
  6. 2026-08-19 18:43 UTCEG score recompute
  7. 2026-08-19 18:43 UTCVendor advisory
  8. 2026-08-19 18:43 UTCGHSA enrichment
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-19 04:45 UTCVendor advisory
  11. 2026-08-19 04:45 UTCGHSA enrichment
  12. 2026-08-18 15:37 UTCEG score recompute
  13. 2026-08-18 15:37 UTCVendor advisory
  14. 2026-08-18 15:37 UTCGHSA enrichment
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-18 02:11 UTCEG score recompute
  17. 2026-08-18 02:11 UTCVendor advisory
  18. 2026-08-18 02:11 UTCGHSA enrichment
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 12:59 UTCVendor advisory
  21. 2026-08-17 12:59 UTCGHSA enrichment
  22. 2026-08-16 23:52 UTCEG score recompute
  23. 2026-08-16 23:52 UTCVendor advisory
  24. 2026-08-16 23:52 UTCGHSA enrichment
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 46 more
  1. 2026-08-16 10:43 UTCEG score recompute
  2. 2026-08-16 10:43 UTCVendor advisory
  3. 2026-08-16 10:43 UTCGHSA enrichment
  4. 2026-08-16 02:14 UTCEPSS rescore
  5. 2026-08-15 21:36 UTCVendor advisory
  6. 2026-08-15 21:36 UTCGHSA enrichment
  7. 2026-08-15 08:28 UTCEG score recompute
  8. 2026-08-15 08:28 UTCVendor advisory
  9. 2026-08-15 08:28 UTCGHSA enrichment
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 19:19 UTCVendor advisory
  12. 2026-08-14 19:19 UTCGHSA enrichment
  13. 2026-08-14 07:59 UTCEG score recompute
  14. 2026-08-14 07:59 UTCVendor advisory
  15. 2026-08-14 07:59 UTCGHSA enrichment
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-13 18:51 UTCVendor advisory
  18. 2026-08-13 18:51 UTCGHSA enrichment
  19. 2026-08-13 05:44 UTCVendor advisory
  20. 2026-08-13 05:44 UTCGHSA enrichment
  21. 2026-08-12 16:35 UTCEG score recompute
  22. 2026-08-12 16:35 UTCVendor advisory
  23. 2026-08-12 16:35 UTCGHSA enrichment
  24. 2026-08-12 16:03 UTCEG score recompute
  25. 2026-08-12 16:03 UTCVendor advisory
  26. 2026-08-12 16:03 UTCGHSA enrichment
  27. 2026-08-12 13:50 UTCEPSS rescore
  28. 2026-08-12 08:26 UTCVendor advisory
  29. 2026-08-12 08:26 UTCGHSA enrichment
  30. 2026-08-11 19:19 UTCEG score recompute
  31. 2026-08-11 19:19 UTCVendor advisory
  32. 2026-08-11 19:18 UTCGHSA enrichment
  33. 2026-08-11 19:04 UTCEG score recompute
  34. 2026-08-11 19:04 UTCVendor advisory
  35. 2026-08-11 19:04 UTCGHSA enrichment
  36. 2026-08-11 18:31 UTCEG score recompute
  37. 2026-08-11 18:31 UTCVendor advisory
  38. 2026-08-11 18:31 UTCGHSA enrichment
  39. 2026-08-11 13:42 UTCEPSS rescore
  40. 2026-08-11 05:23 UTCEG score recompute
  41. 2026-08-11 05:23 UTCGHSA enrichment
  42. 2026-08-11 05:08 UTCEG score recompute
  43. 2026-08-11 05:08 UTCGHSA enrichment
  44. 2026-08-10 21:31 UTCEG score recompute
  45. 2026-08-10 20:55 UTCEG score recompute
  46. 2026-08-10 20:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-18617?
CVE-2026-18617 is a high vulnerability published on August 10, 2026. A flaw was found in the Data Science Pipelines Operator (DSPO). A namespace editor can exploit a vulnerability in the spec.database.customExtraParams field, which allows for the injection of dangerous parameters into the MySQL Data Source Name (DSN) string. By manipulating these parameters, an…
When was CVE-2026-18617 disclosed?
CVE-2026-18617 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18617 actively exploited?
CVE-2026-18617 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 62.5% of all scored CVEs.
What is the CVSS score of CVE-2026-18617?
CVE-2026-18617 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-18617?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18617, 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-18617

Explore →

Is Your Infrastructure Affected by CVE-2026-18617?

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

Start Free Scan →Browse All CVEs