CVE-2026-18617

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM 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.7%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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

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

Patch Availability(6)

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 28× in last 7d / 138× 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 286 total refreshes for this CVE.

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

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 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-18617 actively exploited?
CVE-2026-18617 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18617?
CVE-2026-18617 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18617?
A fix for CVE-2026-18617 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-18617 are linked in the Vendor Advisories panel on this page.

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.