Kubernetes kube-apiserver Vulnerable to Race Condition
CVE-2024-7598GHSA-r56h-j38w-hrqq
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go k8s.io/kubernetes/cmd/kube-apiserver
- Affected
- >= 1.3.0, <= 1.32.3
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-r56h-j38w-hrqq lists affected ranges: Go k8s.io/kubernetes/cmd/kube-apiserver >=1.3.0 <=1.32.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 3.1 · CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2024-7598: 0.32% estimated exploitation activity in the next 30 days; percentile 25.10 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-r56h-j38w-hrqq
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2024-7598 Advisory: Kubernetes kube-apiserver Vulnerable to Race Condition IDs: CVE-2024-7598, GHSA-r56h-j38w-hrqq Record: https://patchnext.com/advisories/cve-2024-7598 (revision 1, source checked 26 Oct 2026, 15:09 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Low (CVSS 3.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - Go k8s.io/kubernetes/cmd/kube-apiserver: affected >= 1.3.0, <= 1.32.3 ## Suggested inspection (read-only) - Go k8s.io/kubernetes/cmd/kube-apiserver: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on k8s.io/kubernetes/cmd/kube-apiserver. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-r56h-j38w-hrqq (GitHub-reviewed advisory GHSA-r56h-j38w-hrqq lists affected ranges: Go k8s.io/kubernetes/cmd/kube-apiserver >=1.3.0 <=1.32.3) Commands are suggestions: review each one before running it.
Loading voting…