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.
Fixes

Solution

This issue has been fixed in the following versions: * v1.21.0 * v1.20.6 * v1.19.10 * v1.18.18


Workaround

No workaround given by the vendor.

History

Thu, 12 Jun 2025 15:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-114
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 13 Feb 2025 16:45:00 +0000

Type Values Removed Values Added
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. 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.

cve-icon MITRE

Status: PUBLISHED

Assigner: kubernetes

Published:

Updated: 2025-06-12T14:42:12.231Z

Reserved: 2021-01-21T21:42:58.237Z

Link: CVE-2021-25736

cve-icon Vulnrichment

Updated: 2024-08-03T20:11:28.044Z

cve-icon NVD

Status : Modified

Published: 2023-10-30T03:15:07.653

Modified: 2025-06-12T15:15:27.407

Link: CVE-2021-25736

cve-icon Redhat

Severity : Moderate

Publid Date: 2021-05-10T00:00:00Z

Links: CVE-2021-25736 - Bugzilla

cve-icon OpenCVE Enrichment

No data.