Advisory record · GHSA-v6q2-4qr3-5cw6

Unencrypted traffic between nodes when using WireGuard and L7 policies

CVSS 6.1 MediumEPSS 0.0017 · 6th percentile

Published by the GitHub Advisory Database at 18 Mar 2024, 20:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/cilium/ciliumGo>=1.14.0, <1.14.8 || >=1.15.0, <1.15.21.14.8, 1.15.2
Identifiers
GHSA-v6q2-4qr3-5cw6 · BIT-cilium-2024-28250 · BIT-cilium-operator-2024-28250 · BIT-cilium-proxy-2024-28250 · BIT-hubble-2024-28250 · BIT-hubble-relay-2024-28250 · BIT-hubble-ui-2024-28250 · BIT-hubble-ui-backend-2024-28250 · CVE-2024-28250 · GO-2024-2657
Weakness (CWE)
CWE-311 · CWE-319
Published
18 Mar 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Cilium (Go module github.com/cilium/cilium) versions 1.14.0 before 1.14.8 and 1.15.0 before 1.15.2 are affected when WireGuard encryption is enabled and traffic matches Layer 7 policies. Traffic between a node's Envoy or DNS proxy and pods on other nodes is sent unencrypted, which can expose it to network observers. Upgrade to 1.14.8 or 1.15.2; in tunneling mode, Cilium 1.14.4 also fixes it if encryption.wireguard.encapsulate is set to true. No workaround is listed.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.1 Medium 3.1 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0017, the 6th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:15 UTC First seen by agentprime
  2. 31 Oct 2026, 14:15 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.