Most recent entries from all

BIT-cilium-2024-52529 — Layer 7 policy enforcement may not occur in policies with wildcarded port ranges in Cilium

2026-10-04T23:04:56.606693+00:00

Affected: Bitnami: cilium

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. For users with the following configuration: 1. An allow policy that selects a Layer 3 destination and a port range `AND` 2. A Layer 7 allow policy that selects a specific port within the first policy's range the Layer 7 enforcement would not occur for the traffic selected by the Layer 7 policy. This issue only affects users who use Cilium's port range functionality, which was introduced in Cilium v1.16. This issue is patched in PR #35150. This issue affects Cilium v1.16 between v1.16.0 and v1.16.3 inclusive. This issue is patched in Cilium v1.16.4. Users are advised to upgrade. Users with network policies that match the pattern described above can work around the issue by rewriting any policies that use port ranges to individually specify the ports permitted for traffic.

EUVD-2026-204358

2026-10-04T23:04:56.606755+00:00

EUVD-2026-204358

fkie_cve-2024-52529

2026-10-04T23:04:56.606771+00:00

GHSA-xg58-75qf-9r67 — Cilium's Layer 7 policy enforcement may not occur in policies with wildcarded port ranges

2026-10-04T23:04:56.606800+00:00

Affected: Go: github.com/cilium/cilium

### Impact

For users with the following configuration:

* An allow policy that selects a [Layer 3 identity](https://docs.cilium.io/en/v1.14/security/policy/language/#layer-3-examples) and a [port range](https://docs.cilium.io/en/stable/security/policy/language/#example-port-ranges) **AND** * A [Layer 7 allow policy](https://docs.cilium.io/en/latest/security/policy/language/#layer-7-examples) that selects a specific port within the first policy's range

then Layer 7 enforcement would not occur for the traffic selected by the Layer 7 policy.

This issue only affects users who use Cilium's port range functionality, which was introduced in Cilium v1.16.

For reference, an example of a pair of policies that would trigger this issue is:

``` apiVersion: "cilium.io/v2" kind: CiliumNetworkPolicy metadata: name: "layer-3-and-4" spec: endpointSelector: matchLabels: app: service ingress: - fromCIDR: - 192.168.60.0/24 toPorts: - ports: - port: "80" endPort: 444 protocol: TCP ``` and ``` apiVersion: "cilium.io/v2" kind: CiliumNetworkPolicy metadata: name: "layer-4-and-7" spec: endpointSelector: matchLabels: app: service ingress: toPorts: - ports: - port: "80" protocol: TCP rules: http: - method: "GET" path: "/public" ```

In the above example, requests would be permitted to all HTTP paths on matching endpoints, rather than just `GET` requests to the `/…

openSUSE-SU-2024:14567-1 — govulncheck-vulndb-0.0.20241209T183251-1.1 on GA media

2026-10-04T23:04:56.606849+00:00

govulncheck-vulndb-0.0.20241209T183251-1.1 on GA media