CVE-2026-120656
Affects OpenKruise kruise-manager up to and including v1.9.1 when pprof is enabled, which is the default. Upgrade to v1.9.2 or later to fix it.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in v1.9.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: v1.9.2.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 7/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in v1.9.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The OpenKruise kruise-manager component, which runs as part of the OpenKruise Kubernetes extension suite, is affected. When its pprof profiling endpoint is enabled, it is exposed without authentication on all network interfaces, so any pod with RBAC access can trigger a denial-of-service condition.
Read the original description
OpenKruise kruise-manager exposes an unauthenticated ppof endpoint when enabled, opening it on 0.0.0.0:8090, which can enable a DoS attack triggerable by any RBAC pod.
What to do
Upgrade to a fixed version: v1.9.2.
Workaround: Add --enable-pprof=false to the kruise-manager container args
Timeline
- CVE published
- First seen by cve.now
Affected versions
- OpenKruise kruise-manager
through 1.9.2
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120656
What does this mean?
The pprof profiling endpoints in kruise-manager were enabled by default and bound to all interfaces. Repeated requests to them can exhaust the manager's memory until it goes NotReady, and because the admission webhooks fail closed, pod creation can be blocked cluster-wide. The endpoints also expose the manager's goroutine stacks and heap profiles.Source: github.com, github.com
Am I affected, and how do I check?
The advisory says kruise-manager up to and including v1.9.1 is affected, and the fix is in v1.9.2. To check a deployment, look at the kruise-manager container args for --enable-pprof; the flag defaults to true when it is not set.Source: github.com, github.com
What should I do about it?
Upgrade kruise-manager to v1.9.2 or later. If an upgrade is not possible yet, add --enable-pprof=false to the kruise-manager container args.Source: github.com, github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data