OpenKruise kruise-manager exposes an unauthenticated ppof endpoint when enabled, opening it on 0.0.0.0:8090, which can
Source GCVE Database
Not known to be exploited.
Data as of 2 Nov 2026, 23:28 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenKruisekruise-manager | Affected
| Fixed in– |
AI-suggested
Users should consider disabling the ppof endpoint if not needed or restricting network access to port 8090.
Description
OpenKruise's kruise-manager component exposes an unauthenticated ppof endpoint on all network interfaces (0.0.0.0) at port 8090 when enabled. This exposure allows any pod with RBAC permissions to trigger a denial-of-service (DoS) attack against the service.