CVE-2026-24005
Prior to versions 1.8.3 and 1.7.5, PodProbeMarker allows defining custom probes with TCPSocket or HTTPGet handlers.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.29%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
Kruise provides automated management of large-scale applications on Kubernetes. Prior to versions 1.8.3 and 1.7.5, PodProbeMarker allows defining custom probes with TCPSocket or HTTPGet handlers. The webhook validation does not restrict the Host field in these probe configurations. Since kruise-daemon runs with hostNetwork=true, it executes probes from the node network namespace. An attacker with PodProbeMarker creation permission can specify arbitrary Host values to trigger SSRF from the node, perform port scanning, and receive response feedback through NodePodProbe status messages. Versions 1.8.3 and 1.7.5 patch the issue.
- CVSS 3.1
- 7.6 HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
- EPSS
- 0.29% probability · 21th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-918
- Affected
- openkruise/kruise
- Source
- security-advisories@github.com
References
- https://github.com/openkruise/kruise/commit/94364b76adf3e8a1749a31afe809a163bed29613Patch
- https://github.com/openkruise/kruise/releases/tag/v1.7.5Product, Release Notes
- https://github.com/openkruise/kruise/releases/tag/v1.8.3Product, Release Notes
- https://github.com/openkruise/kruise/security/advisories/GHSA-9fj4-3849-rv9gExploit, Mitigation, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.