Cilium's CIDR deny policies may not take effect when a more narrow CIDR allow is present
Published Oct 21, 2024 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
Cilium's CIDR deny policies may not take effect when a more narrow CIDR allow is present
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
A policy rule denying a prefix that is broader than /32 may be ignored if there is
Potential 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:
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Oct 21, 2024 · Last refreshed Nov 3, 2026