CVE-2021-25736: Windows kube-proxy LoadBalancer contention
Vendor fix available · Affected: Kubernetes · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 60% of scored CVEs
DescriptionCVE.org
Kube-proxy on Windows can unintentionally forward traffic to local processes listening on the same port (“spec.ports[*].port”) as a LoadBalancer Service when the LoadBalancer controller does not set the “status.loadBalancer.ingress[].ip” field. Clusters where the LoadBalancer controller sets the “status.loadBalancer.ingress[].ip” field are unaffected.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Kubernetes · Kubernetesup to and including v1.20.5
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Kubernetes
- Published
- October 2023
CoverageNo articles yet
No CyberSIXT article names CVE-2021-25736 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.