Advisory record · GHSA-xg58-75qf-9r67

Cilium's Layer 7 policy enforcement may not occur in policies with wildcarded port ranges

CVSS 5.8 MediumEPSS 0.0052 · 44th percentile

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

PackageEcosystemAffectedFixed in
github.com/cilium/ciliumGo>=1.16.0, <1.16.41.16.4
Identifiers
GHSA-xg58-75qf-9r67 · BIT-cilium-2024-52529 · BIT-cilium-operator-2024-52529 · BIT-hubble-relay-2024-52529 · CVE-2024-52529 · GO-2024-3290
Weakness (CWE)
CWE-755 · CWE-862
Published
25 Nov 2024
Updated
10 Sept 2026

Machine-written summary

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

Cilium (github.com/cilium/cilium) versions 1.16.0 through 1.16.3 are affected. When a Layer 3 and 4 allow policy uses a port range and a Layer 7 allow policy targets a port inside that range, Layer 7 enforcement may not apply to traffic the Layer 7 policy selects, so requests can be permitted on paths the Layer 7 policy was meant to restrict. Upgrade to Cilium 1.16.4. As a workaround, rewrite policies that use port ranges to list each permitted port individually.

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
5.8 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0052, the 44th 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.