GHSA-WC5V-R48V-G4VH

Workarounds

For affected users who can't upgrade, one potential workaround is to ensure all pods have network policies that prevent sending arbitrary traffic to the local node.

References

Commit fixing the vulnerability: https://github.com/cilium/cilium/commit/c758da7e9d19cd19b96dc90424c0b5ec7409cd0a.

For more information

If you have any questions or comments about this advisory, please reach out on Slack.

As usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: [email protected], first, before disclosing them in any public forums. This is a private mailing list where only members of the Cilium internal security team are subscribed to, and is treated as top priority.

This vulnerability allows bypassing host policies for IPv6 traffic coming from a Cilium-managed pod and destined to the host-network namespace (e.g., to a host-network pod). Host policy enforcement on IPv4 or for traffic coming from outside the node is not affected.

Cilium is only affected by this vulnerability if IPv4, IPv6, endpoint routes, and the host firewall are enabled. Note that endpoint routes are typically only enabled in GKE, EKS, AKS, and OpenShift; in those environments, IPv6 is typically disabled. Host firewall is disabled by default.

GHSA-WC5V-R48V-G4VH has a CVSS score of 3.3 (Low). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.10.13, 1.11.7); upgrading removes the vulnerable code path.

Kodem intelligence

The bug is fixed in versions v1.10.13 and v1.11.7 of Cilium.

1. What is GHSA-WC5V-R48V-G4VH? GHSA-WC5V-R48V-G4VH is a low-severity security vulnerability in github.com/cilium/cilium (go), affecting versions < 1.10.13. It is fixed in 1.10.13, 1.11.7.
2. How severe is GHSA-WC5V-R48V-G4VH? GHSA-WC5V-R48V-G4VH has a CVSS score of 3.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/cilium/cilium are affected by GHSA-WC5V-R48V-G4VH? github.com/cilium/cilium (go) versions < 1.10.13 is affected.
4. Is there a fix for GHSA-WC5V-R48V-G4VH? Yes. GHSA-WC5V-R48V-G4VH is fixed in 1.10.13, 1.11.7. Upgrade to this version or later.
5. Is GHSA-WC5V-R48V-G4VH exploitable, and should I be worried? Whether GHSA-WC5V-R48V-G4VH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-WC5V-R48V-G4VH is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-WC5V-R48V-G4VH?
   • Upgrade github.com/cilium/cilium to 1.10.13 or later
   • Upgrade github.com/cilium/cilium to 1.11.7 or later

Other vulnerabilities in github.com/cilium/cilium