# CVE-2024-7598: Network restriction bypass via race condition during namespace termination

> A race condition during namespace deletion allows compromised pods to bypass network policy restrictions temporarily.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2025
- **Updated:** 20 Mar 2025
- **Also known as:** AZL-58953, AZL-58960, CLEANSTART-2026-RO24515, DEBIAN-CVE-2024-7598, ECHO-fd52-1a86-4159, GHSA-r56h-j38w-hrqq, GO-2025-3547, MINI-2f9m-h4qp-h9c8, MINI-2hvj-j4m7-qggg, MINI-3355-gh48-xp22, MINI-375p-42p4-x78r, MINI-39vr-2cr4-mqjr, MINI-3jgm-642g-5c7h, MINI-3mfp-3fvm-mxpr, MINI-4698-mcvp-25pg, MINI-4c7x-mcwh-7rc6, MINI-59h6-vm69-36mq, MINI-5c79-77r5-rrqv, MINI-5j3p-29w9-38fv, MINI-5rhj-qr73-qm6g, MINI-6426-xwvh-2qxv, MINI-645j-fgq3-vv5p, MINI-6769-2cp8-6x43, MINI-6rmf-8v2v-gqg8, MINI-6vrf-cm6f-23r3, MINI-723v-xwjj-xp2x, MINI-73v5-5pq4-qm2v, MINI-74mr-rq9w-cqh4, MINI-79p4-pvv9-q8cf, MINI-7c4x-5qf2-4h86, MINI-8c64-fp82-jrfx, MINI-8pqh-5w4f-62gw, MINI-8xq9-gj9g-8jgg, MINI-97q4-4mv2-8jcf, MINI-9953-7m86-6558, MINI-9hwq-g8j2-3wwh, MINI-9jfv-7f5m-g7vm, MINI-c9cr-2fhr-4vx9, MINI-cq46-287v-jg68, MINI-fgf4-cvwr-g3x6, MINI-fqw2-2j3r-4pjm, MINI-g5m3-prc2-pwhx, MINI-gcrf-3j3w-35wf, MINI-gpww-h6qc-vxhq, MINI-h6fw-q69c-vrjj, MINI-h9c5-42xm-r83q, MINI-hh52-h9pg-f4pm, MINI-hw3j-g3jh-3cpc, MINI-j92w-244h-5f2r, MINI-jgqc-4vq7-4gq6, MINI-jqxr-q5r4-v73g, MINI-jxmf-pf77-3v65, MINI-m43p-82r9-85v3, MINI-m5q4-56vv-49w7, MINI-mcq5-26qc-xg44, MINI-mh9x-fhm3-p4m3, MINI-mrwf-xfg5-783m, MINI-q7mf-4hm9-4ggw, MINI-r2ww-cj2x-fmpw, MINI-r89x-5hq6-g2rc, MINI-r9ch-gg67-94m7, MINI-rjqg-2mq8-mxcp, MINI-rwg4-9vmw-h5f8, MINI-rwhw-c4ff-ggr5, MINI-v7vw-6vj9-f672, MINI-v887-pv8q-h7fx, MINI-vmjp-vxpv-2994, MINI-vrgq-53x8-mwf3, MINI-ww57-8mcc-9cfw, MINI-x4qw-vpw3-m6r5, MINI-x6vv-f86j-q973, MINI-x9cq-jcxp-6hw2

## What is CVE-2024-7598?

CVE-2024-7598 is a low-severity vulnerability in Kubernetes kube-apiserver, published on 20 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security issue was discovered in Kubernetes where a malicious or compromised pod could bypass network restrictions enforced by network policies during namespace deletion. The order in which objects are deleted during namespace termination is not defined, and it is possible for network policies to be deleted before the pods that they protect. This can lead to a brief period in which the pods are running, but network policies that should apply to connections to and from the pods are not enforced.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2024-7598?

3 open source packages ship an affected version, including k8s.io/kubernetes/cmd/kube-apiserver and k8s.io/kubernetes.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `k8s.io/kubernetes/cmd/kube-apiserver` | Go | From 1.3.0 to 1.32.3 | None |
| `k8s.io/kubernetes/cmd/kube-apiserver` | Go | From 1.3.0 to 1.32.3 | None |
| `k8s.io/kubernetes` | Go | From 1.3.0 | None |

## How do I fix CVE-2024-7598?

Apply the vendor's patch.

## Is CVE-2024-7598 being exploited?

There is no known exploitation of CVE-2024-7598 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7598 and fix it if it is affected.

What it is: CVE-2024-7598 is a low-severity vulnerability in Kubernetes kube-apiserver, published on 20 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7598 in the wild and no public exploit code.

Affected packages and fixed versions:
- k8s.io/kubernetes/cmd/kube-apiserver (Go): affected from 1.3.0 up to 1.32.3; no fix listed
- k8s.io/kubernetes/cmd/kube-apiserver (Go): affected from 1.3.0 up to 1.32.3; no fix listed
- k8s.io/kubernetes (Go): affected from 1.3.0; no fix listed

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-2024-7598/ (Markdown: https://insights.sbomify.com/CVE-2024-7598/index.md)
```

## Sources

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

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