# CVE-2026-24005: OpenKruise PodProbeMarker is Vulnerable to SSRF via Unrestricted Host Field

> Attackers with PodProbeMarker permissions can trigger SSRF from the node network namespace to scan ports and read responses.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Feb 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-9fj4-3849-rv9g, GO-2026-4549

## What is CVE-2026-24005?

CVE-2026-24005 is a server-side request forgery vulnerability in openkruise kruise, published on 25 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-24005?

5 open source packages ship an affected version, including github.com/openkruise/kruise. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openkruise/kruise` | Go | All versions | 1.7.5, 1.8.3 |
| `github.com/openkruise/kruise` | Go | All versions | 1.7.5 |
| `github.com/openkruise/kruise` | Go | All versions | 1.7.5 |
| `github.com/openkruise/kruise` | Go | From 1.8.0 | 1.8.3 |
| `github.com/openkruise/kruise` | Go | From 1.8.0 | 1.8.3 |

Products: Openkruise Kruise.

## How do I fix CVE-2026-24005?

Upgrade github.com/openkruise/kruise to a fixed version for your release line: 1.7.5 or 1.8.3.

## Is CVE-2026-24005 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24005 exists.

## Other vulnerabilities in openkruise kruise

- [CVE-2023-30617](https://insights.sbomify.com/CVE-2023-30617/): Leverage the kruise-daemon pod to list all secrets in the entire cluster (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24005 and fix it if it is affected.

What it is: CVE-2026-24005 is a server-side request forgery vulnerability in openkruise kruise, published on 25 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24005 exists.

Affected packages and fixed versions:
- github.com/openkruise/kruise (Go): affected all versions; fixed in 1.7.5, 1.8.3
- github.com/openkruise/kruise (Go): affected all versions; fixed in 1.7.5
- github.com/openkruise/kruise (Go): affected all versions; fixed in 1.7.5
- github.com/openkruise/kruise (Go): affected from 1.8.0; fixed in 1.8.3
- github.com/openkruise/kruise (Go): affected from 1.8.0; fixed in 1.8.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24005/ (Markdown: https://insights.sbomify.com/CVE-2026-24005/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24005
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24005
- OSV: https://osv.dev/vulnerability/CVE-2026-24005

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24005/
Summaries are generated and may contain mistakes; the official description above is the record.