CVE-2026-50125

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th 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
Elevated
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

MKP is a Model Context Protocol server for Kubernetes. Prior to 0.4.1, cmd/server/main.go exposes the default HTTP endpoint and pkg/mcp/server.go registers the unauthenticated get_resource tool, which accepts attacker-controlled limitBytes and tailLines values for the pods logs subresource. buildPodLogOpts() in pkg/k8s/subresource.go parses those values as unbounded int64 parameters, and defaultGetPodLogs() copies the returned Kubernetes log stream through io.Copy into an in-memory bytes.Buffer without an application-side cap. A remote attacker who can reach the default port 8080 MCP endpoint and select a pod with sufficiently large accumulated logs can send one tools/call request that causes large allocations and additional response copies, while the request-frequency limiter does not constrain per-request volume. This can exhaust process memory, terminate the MKP server, and deny the MCP service; observed testing showed more than one GiB of RSS growth while handling a 128 MiB requested stream. This issue is fixed in version 0.4.1.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

July 14, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 17, 2026
Patch available. Sources: github, github_commit.
GitHub commit Patch Available

commit 37bf6bac862a (StacklokLabs/mkp)

Patch available: StacklokLabs/mkp v0.4.3 (contains commit 37bf6bac862a)

https://github.com/StacklokLabs/mkp/commit/37bf6bac862aa3b1c71b8aa1b8364eae7818962d
GitHub advisoryMentions a patch (unverified)

Unbounded Pod Log Read via Attacker-Controlled `limitBytes`/`tailLines` Causes Memory Exhaustion · Advisory · StacklokLabs/mkp · GitHub

https://github.com/StacklokLabs/mkp/security/advisories/GHSA-qw5r-ppcg-f8rj

Vendor Advisories for CVE-2026-50125(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/StacklokLabs/mkp—
  • every version up to 0.4.1: fixed in 0.4.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 31× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-10-12 15:59 UTCEG score recompute
  4. 2026-10-11 19:42 UTCEG score recompute
  5. 2026-10-11 16:57 UTCEG score recompute
  6. 2026-10-11 14:21 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-09-30 17:53 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-09-28 08:56 UTCEG score recompute
  22. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-09-24 21:26 UTCEG score recompute
Show 10 more
  1. 2026-09-24 09:01 UTCEG score recompute
  2. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-09-23 03:32 UTCEG score recompute
  4. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  6. 2026-09-17 20:18 UTCEG score recompute
  7. 2026-07-30 13:16 UTCEG score recompute
  8. 2026-07-26 11:43 UTCEG score recompute
  9. 2026-07-23 03:18 UTCEG score recompute
  10. 2026-07-14 18:10 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50125?
CVE-2026-50125 is a high-severity vulnerability; its CVE record was published on July 14, 2026. MKP is a Model Context Protocol server for Kubernetes. Prior to 0.4.1, cmd/server/main.go exposes the default HTTP endpoint and pkg/mcp/server.go registers the unauthenticated get_resource tool, which accepts attacker-controlled limitBytes and tailLines values for the pods logs subresource.…
When was the CVE record for CVE-2026-50125 published?
The CVE record for CVE-2026-50125 was published on July 14, 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 September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-50125 actively exploited?
CVE-2026-50125 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50125?
CVE-2026-50125 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50125?
A fix for CVE-2026-50125 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50125 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-50125

Explore →

Is Your Infrastructure Affected by CVE-2026-50125?

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

Book a Demo →Browse All CVEs