# CVE-2026-50125: StacklokLabs MKP denial of service via unbounded pod log read

Source: https://junglewise.ai/threats/cve-2026-50125-stackloklabs-mkp-denial-of-service-via-unbounded-pod-log-read  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-17. Updated: 2026-07-14  
License: CC BY 4.0 with a link back

CVE-2026-50125 · Severity: high · CVSS 7.5 · Published 2026-09-17

The MKP (Model Context Protocol for Kubernetes) server, which helps manage Kubernetes cluster data, contains a flaw that allows an unauthenticated attacker to crash the service. By requesting extremely large log files from a container, an attacker can force the server to use up all available memory, leading to a complete service outage. This can disrupt operations for any team relying on MKP for cluster monitoring and observability.

Vendors: [Go](https://junglewise.ai/threats/vendors/go), [Stacklok](https://junglewise.ai/threats/vendors/stacklok).

## Quick answers

**Is CVE-2026-50125 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-50125 being exploited in the wild.

**How severe is CVE-2026-50125?** High severity, with a CVSS score of 7.5, published 17 September 2026.

**Which products and versions are affected?** github.com/StacklokLabs/mkp (Go) < 0.4.1, SEMVER:introduced=0,fixed=0.4.1; Stacklok Mkp < 0.4.1.

**Is there a fix for CVE-2026-50125?** Yes. github.com/StacklokLabs/mkp (Go): upgrade to 0.4.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-50125 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-50125?** Check whether you run github.com/StacklokLabs/mkp (Go) or Stacklok Mkp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/StacklokLabs/mkp (Go): upgrade to 0.4.1 or later

  ```sh
  go get github.com/StacklokLabs/mkp@v0.4.1
  ```


## Technical details

The vulnerability is located in the `get_resource` MCP tool within `pkg/k8s/subresource.go`. The server parses user-supplied `limitBytes` and `tailLines` parameters as `int64` values without enforcing any upper bounds. These values are passed to the Kubernetes API, and the resulting log stream is read into an in-memory `bytes.Buffer` using `io.Copy`. Because there is no application-side size limit, a single crafted `tools/call` request can trigger an Out-of-Memory (OOM) kill. The vulnerability is exploitable remotely without authentication in the default configuration. Version 0.4.1 introduces hard caps on log retrieval sizes to mitigate this issue.

## Affected products

- StacklokLabs mkp < 0.4.1

## Identifiers

- CVE-2026-50125
- GHSA-qw5r-ppcg-f8rj
- GO-2026-5978

## Timeline

- 2026-06-10: disclosed: Initial disclosure on GitHub
- 2026-07-14: advisory: Advisory published/updated

## References

- [https://api.github.com/users/EQSTLab](https://api.github.com/users/EQSTLab)
- [https://github.com/EQSTLab](https://github.com/EQSTLab)
- [https://api.github.com/users/EQSTLab/gists%7B/gist_id%7D](https://api.github.com/users/EQSTLab/gists%7B/gist_id%7D)
- [https://api.github.com/users/EQSTLab/repos](https://api.github.com/users/EQSTLab/repos)
- [https://avatars.githubusercontent.com/u/148991397?v=4](https://avatars.githubusercontent.com/u/148991397?v=4)
- [https://api.github.com/users/EQSTLab/events%7B/privacy%7D](https://api.github.com/users/EQSTLab/events%7B/privacy%7D)