CVE-2026-130007

HIGHPre-NVD 7.97.9
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (45th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-129038 (ENISA EUVD) · GHSA-m932-63jc-4jqq (GitHub Security Advisories)Source: ENISA EUVD

7.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

k8s-mcp-server manages Kubernetes clusters through the Model Context Protocol. Prior to 1.1.0, SERVER_MODE defaults to SSE, with the listener on 0.0.0.0:8080, but main.go creates the SSE server without an authentication option or context function. The GET /sse handler creates a sessionId that is only a correlation value, and the POST /message handler accepts a loadable sessionId without an authorization or Origin check before dispatching tools/call; consequently, any client able to reach the port can enumerate and invoke registered Kubernetes tools without credentials. Read-only mode is disabled by default, leaving write-capable Kubernetes tools available to run with the server's configured cluster privileges. This issue is fixed in version 1.1.0.

CVSS
7.9
EG Score
7.9HIGHmedium confidence
EG Risk
36
EG Risk 36/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)
Severity79% × 45%
Impact severity (EG Severity): CVSS 7.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.5%
EPSS %ILE
45th
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 (7.9): severity, escalated by confirmed exploitation. This CVE's 7.9 is its impact severity (EG Severity), not escalated.

EG Severity
7.9 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS. 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 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). 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)14 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 total (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 18, 2026

Last Modified

November 21, 2026

Advisory Details (5)

Auto-updated Nov 18, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available

v1.1.0

Patch available: reza-gholizade/k8s-mcp-server v1.1.0

https://github.com/reza-gholizade/k8s-mcp-server/releases/tag/v1.1.0
GitHub commit Patch Available

commit 817d81005369 (reza-gholizade/k8s-mcp-server)

Patch available: reza-gholizade/k8s-mcp-server v1.1.0 (contains commit 817d81005369)

https://github.com/reza-gholizade/k8s-mcp-server/commit/817d81005369837e0c034962785851ca4dec9a76
GitHub pull request Patch Available

Secure MCP HTTP transports by default

Patch available: reza-gholizade/k8s-mcp-server v1.1.0 (PR #134 merged 2026-08-19)

https://github.com/reza-gholizade/k8s-mcp-server/pull/134
Web page🟡 PoC Available

Security: how to report a vulnerability privately? · Issue #131 · reza-gholizade/k8s-mcp-server · GitHub

https://github.com/reza-gholizade/k8s-mcp-server/issues/131
GitHub advisoryMentions a patch (unverified)

Missing authentication on default SSE/HTTP transport allows unauthenticated Kubernetes tool execution (CWE-306) · Advisory · reza-gholizade/k8s-mcp-server · GitHub

https://github.com/reza-gholizade/k8s-mcp-server/security/advisories/GHSA-m932-63jc-4jqq

Vendor Advisories for CVE-2026-130007(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/reza-gholizade/k8s-mcp-server @ 1.1.0 (fixes < 1.1.0)—ghsa

These rows come from GitHub (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/reza-gholizade/k8s-mcp-server—
  • every version up to 1.1.0: fixed in 1.1.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 9× 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 → 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-21 16:38 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  2. 2026-11-21 05:28 UTCEchelonGraph re-scored
  3. 2026-11-21 05:28 UTCGHSA enrichmentGHSA-m932-63jc-4jqq · GitHub severity HIGH
  4. 2026-11-21 04:21 UTCEchelonGraph re-scored
  5. 2026-11-21 04:21 UTCGHSA enrichmentGHSA-m932-63jc-4jqq · GitHub severity HIGH
  6. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-11-20 01:27 UTCEchelonGraph re-scored
  8. 2026-11-20 01:27 UTCGHSA enrichmentGHSA-m932-63jc-4jqq · GitHub severity HIGH
  9. 2026-11-19 20:56 UTCOSV refresh
  10. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-11-18 18:03 UTCENISA EUVD ID recordedEUVD-2026-129038 · Source: ENISA EUVD
  12. 2026-11-18 17:28 UTCEchelonGraph re-scored
  13. 2026-11-18 16:43 UTCEchelonGraph re-scoredFirst assessed: 7.9 HIGH
  14. 2026-11-18 16:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-130007?
CVE-2026-130007 is a high-severity vulnerability; its CVE record was published on November 18, 2026. k8s-mcp-server manages Kubernetes clusters through the Model Context Protocol. Prior to 1.1.0, SERVER_MODE defaults to SSE, with the listener on 0.0.0.0:8080, but main.go creates the SSE server without an authentication option or context function. The GET /sse handler creates a sessionId that is…
When was the CVE record for CVE-2026-130007 published?
The CVE record for CVE-2026-130007 was published on November 18, 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 21, 2026; the record at its source may have been updated since.
Is CVE-2026-130007 actively exploited?
CVE-2026-130007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-130007?
CVE-2026-130007 has a CVSS base score of 7.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-130007?
A fix for CVE-2026-130007 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-130007 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-130007

Explore →

Is Your Infrastructure Affected by CVE-2026-130007?

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