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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.0 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

EPSS

• CVE-2024-47825: 0.40% estimated exploitation activity in the next 30 days; percentile 33.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact A policy rule denying a prefix that is broader than /32 may be ignored if there is - A policy rule referencing a more narrow prefix (CIDRSet or toFQDN) and - This narrower policy rule specifies either enableDefaultDeny: false or - toEntities: all Note that a rule specifying toEntities: world or toEntities: 0.0.0.0/0 is insufficient, it must be to entity all. As an example, given the below policies, traffic is allowed to 1.1.1.2, when it should be denied: Patches This issue affects: - Cilium v1.14 between v1.14.0 and v1.14.15 inclusive - Cilium v1.15 between v1.15.0 and v1.15.9 inclusive This issue has been patched in: - Cilium v1.14.16 - Cilium v1.15.10 Workarounds Users with policies using enableDefaultDeny: false can work around this issue by removing this configuration option and explicitly defining any allow rules required. No workaround is available to users with egress policies that explicitly specify toEntities: all. Acknowledgements The Cilium community has worked…

Published by the source

21 Oct 2024, 19:03 UTC

Last modified by the source

1 Nov 2024, 19:58 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3wwx-63fv-pfq6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-47825

Advisory: Cilium's CIDR deny policies may not take effect when a more narrow CIDR allow is present
IDs: CVE-2024-47825, GHSA-3wwx-63fv-pfq6
Record: https://patchnext.com/advisories/cve-2024-47825 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/cilium/cilium 1.15.10, 1.14.16. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cilium/cilium: affected >= 1.15.0, < 1.15.10; >= 1.14.0, < 1.14.16; fixed in 1.15.10, 1.14.16

## Suggested inspection (read-only)
- Go github.com/cilium/cilium: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cilium/cilium.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3wwx-63fv-pfq6 (GitHub-reviewed advisory GHSA-3wwx-63fv-pfq6 lists affected ranges: Go github.com/cilium/cilium >=1.15.0 =1.14.0 <1.14.16)

Commands are suggestions: review each one before running it.