NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

Unencrypted traffic between nodes when using WireGuard and L7 policiesGHSA-v6q2-4qr3-5cw6

MEDIUM

GHSA-v6q2-4qr3-5cw6 is a medium-severity (CVSS 6.1) CWE-311 vulnerability in github.com/cilium/cilium. A fix is available for github.com/cilium/cilium — see the affected versions and patch details below.

Also known asBIT-cilium-2024-28250BIT-cilium-operator-2024-28250BIT-cilium-proxy-2024-28250BIT-hubble-2024-28250BIT-hubble-relay-2024-28250BIT-hubble-ui-2024-28250
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-v6q2-4qr3-5cw6.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk+0.12%
Lower risk than most CVEs7th percentile — riskier than 7% of all scored CVEsHighest risk
0.00%0.22%0.45%0.67%0.1%0.1%0.2%May 26Jun 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐹github.com/cilium/cilium🐹github.com/cilium/cilium

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

In Cilium clusters with WireGuard enabled and traffic matching Layer 7 policies:

  • Traffic that should be WireGuard-encrypted is sent unencrypted between a node's Envoy proxy and pods on other nodes.
  • Traffic that should be WireGuard-encrypted is sent unencrypted between a node's DNS proxy and pods on other nodes.

Patches

This issue affects:

  • In native routing mode (routingMode=native):
    • Cilium v1.14 versions before v1.14.8
    • Cilium v1.15 versions before v1.15.2
  • In tunneling mode (routingMode=tunnel):
    • Cilium v1.14 versions before v1.14.4
    • Cilium v1.14.4 if encryption.wireguard.encapsulate is set to false (default).

This issue has been resolved in:

  • In native routing mode (routingMode=native):
    • Cilium v1.14.8
    • Cilium v1.15.2
  • In tunneling mode (routingMode=tunnel):
    • Cilium v1.14.4. NOTE encryption.wireguard.encapsulate must be set to true.

Workarounds

There is no workaround to this issue.

Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @brb, @giorio94, @gandro and @jschwinger233 for their work on triaging and remediating this issue.

For more information

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

If you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list at [email protected]. This is a private mailing list where only members of the Cilium internal security team are subscribed to, and your report will be treated as top priority.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/cilium/cilium≥ 1.14.0&&< 1.14.81.14.8go get github.com/cilium/cilium@v1.14.8
🐹Gogithub.com/cilium/cilium≥ 1.15.0&&< 1.15.21.15.2go get github.com/cilium/cilium@v1.15.2

Affected Products

1 product · 2 configurations
Application
ciliumcilium
≥ 1.15.0 && < 1.15.2
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cilium/cilium, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/cilium/cilium to 1.14.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v6q2-4qr3-5cw6 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact In Cilium clusters with WireGuard enabled and traffic matching Layer 7 policies: - Traffic that should be WireGuard-encrypted is sent unencrypted between a node's Envoy proxy and pods on other nodes. - Traffic that should be WireGuard-encrypted is sent unencrypted between a node's DNS proxy and pods on other nodes. ### Patches This issue affects: * In native routing mode (`routingMode=native`): * Cilium v1.14 versions before v1.14.8 * Cilium v1.15 versions before v1.15.2 * In tunneling mode (`routingMode=tunnel`): * Cilium v1.14 versions before v1.14.4 * Cilium v1.14.4
O3 Security · Impact-Aware SCA

Is GHSA-v6q2-4qr3-5cw6 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Unencrypted traffic between nodes when using…