Advisory record · GHSA-3wwx-63fv-pfq6

Cilium's CIDR deny policies may not take effect when a more narrow CIDR allow is present

CVSS 4.0 MediumEPSS 0.0040 · 34th percentile

Published by the GitHub Advisory Database at 21 Oct 2024, 19:03 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/cilium/ciliumGo>=1.15.0, <1.15.10 || >=1.14.0, <1.14.161.15.10, 1.14.16
Identifiers
GHSA-3wwx-63fv-pfq6 · BIT-cilium-2024-47825 · BIT-cilium-operator-2024-47825 · BIT-hubble-relay-2024-47825 · CVE-2024-47825 · GO-2024-3208
Weakness (CWE)
CWE-276 · CWE-1038
Published
21 Oct 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 through 1.14.15 and 1.15.0 through 1.15.9 are affected. A deny policy for a prefix broader than /32 can be ignored when a narrower CIDRSet or toFQDN allow rule also sets enableDefaultDeny: false or toEntities: all, so traffic that should be denied gets through. Upgrade to 1.14.16 or 1.15.10. Users with enableDefaultDeny: false can remove that option and define needed allow rules explicitly; no workaround is listed for policies using toEntities: all.

Written 1 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
4.0 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0040, the 34th percentile, on 5 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.