CVE-2026-88982

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.4 from GitHub Security Advisory (severity: MODERATE) published 2026-11-09. A secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-117831 (ENISA EUVD) · GHSA-2xwh-426q-42c5 (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the legacy V1/raw-Argo execution cache mutating webhook and cache-server storage path hash selected template fields without the Kubernetes namespace, use the key alone for lookups and duplicate checks, and trust the mutable pipelines.kubeflow.org/execution_cache_key annotation when publishing outputs. In multi-user deployments where tenant namespaces share the cache service, a tenant with workload-submission privileges can read another namespace's cached outputs or seed matching outputs that are substituted into a later step. Standard KFP V2 component pods bypass this cache, matching requires the selected template fields and staleness policy, and arbitrary code execution or service availability impact is not established. This issue is fixed in version 2.18.0.

CVSS v3
5.4
EG Score
5.4MEDIUMhigh confidence
EG Risk
24
EG Risk 24/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
4th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 5, 2026

Last Modified

November 10, 2026

Advisory Details (4)

Auto-updated Nov 6, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)

Cross-tenant execution-cache poisoning / output substitution via a namespace-blind cache key in the Kubeflow Pipelines cache webhook (multi-user) · Advisory · kubeflow/pipelines · GitHub

https://github.com/kubeflow/pipelines/security/advisories/GHSA-2xwh-426q-42c5
GitHub release Patch Available

Version 2.18.0

Patch available: kubeflow/pipelines 2.18.0

https://github.com/kubeflow/pipelines/releases/tag/2.18.0
GitHub pull request Patch Available

fix(backend): isolate legacy execution cache by namespace

Patch available: kubeflow/pipelines sdk-2.18.0 (PR #14359 merged 2026-09-10)

https://github.com/kubeflow/pipelines/pull/14359
GitHub commit Patch Available

commit 620d0cc89ae0 (kubeflow/pipelines)

Patch available: kubeflow/pipelines sdk-2.18.0 (contains commit 620d0cc89ae0)

https://github.com/kubeflow/pipelines/commit/620d0cc89ae0d042a484a003f8ffe6e9a55d347e

Vendor Advisories for CVE-2026-88982(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/kubeflow/pipelines @ 0.0.0-20260910172610-620d0cc89ae0 (fixes < 0.0.0-20260910172610-620d0cc89ae0)—ghsa

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.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/kubeflow/pipelines—
  • every version up to 0.0.0-20260910172610-620d0cc89ae0: fixed in 0.0.0-20260910172610-620d0cc89ae0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 12× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  2. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  3. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  4. 2026-11-10 05:27 UTCEchelonGraph re-scored
  5. 2026-11-10 05:27 UTCGHSA enrichmentGHSA-2xwh-426q-42c5 · GitHub severity MODERATE · GitHub CVSS 5.4
  6. 2026-11-10 04:50 UTCEchelonGraph re-scored
  7. 2026-11-10 04:50 UTCGHSA enrichmentGHSA-2xwh-426q-42c5 · GitHub severity MODERATE · GitHub CVSS 5.4
  8. 2026-11-09 22:45 UTCEchelonGraph re-scored
  9. 2026-11-09 22:45 UTCGHSA enrichmentGHSA-2xwh-426q-42c5 · GitHub severity MODERATE · GitHub CVSS 5.4
  10. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  11. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  12. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  13. 2026-11-06 21:48 UTCEchelonGraph re-scored
  14. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  15. 2026-11-05 23:28 UTCEchelonGraph re-scored
  16. 2026-11-05 23:04 UTCENISA EUVD ID recordedEUVD-2026-117831 · Source: ENISA EUVD
  17. 2026-11-05 22:33 UTCEchelonGraph re-scoredFirst assessed: 5.4 MEDIUM
  18. 2026-11-05 22:32 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-88982?
CVE-2026-88982 is a medium-severity vulnerability; its CVE record was published on November 5, 2026. Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the legacy V1/raw-Argo execution cache mutating webhook and cache-server storage path hash selected template fields without the Kubernetes namespace, use the key alone for lookups…
When was the CVE record for CVE-2026-88982 published?
The CVE record for CVE-2026-88982 was published on November 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 10, 2026; the record at its source may have been updated since.
Is CVE-2026-88982 actively exploited?
CVE-2026-88982 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-88982?
CVE-2026-88982 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-88982?
A fix for CVE-2026-88982 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-88982 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-88982

Explore →

Is Your Infrastructure Affected by CVE-2026-88982?

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

Book a Demo →Browse All CVEs