Cilium 1.16.0
Approved changes feed: RSS · Atom
cpe:2.3:a:cilium:cilium:1.16.0:*:*:*:*:*:*:*
part: a version: 1.16.0 update: *
| Vendor | Cilium (d232e85e-ece2-5fac-ab02-abc58e426d85) |
|---|---|
| Product | Cilium (f263902e-55a2-544d-80da-1c950d1ea6f8) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:docker/cilium/cilium |
purl2cpe | 2026-06-01 10:17:12.283017 |
pkg:github/cilium/cilium |
purl2cpe | 2026-06-01 10:17:12.283018 |
pkg:rpm/opensuse/cilium |
purl2cpe | 2026-06-01 10:17:12.283020 |
pkg:sourceforge/cilium.mirror |
purl2cpe | 2026-06-01 10:17:12.283022 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-42487 |
vulnerable | 2026-06-08 06:45:46.556108 |
Cilium's Gateway API route matching order contradicts specification
MEDIUM (4)
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In the 1.15 branch prior to 1.15.8 and the 1.16 branch prior to 1.16.1, Gateway API HTTPRoutes and GRPCRoutes do not follow the match precedence specified in the Gateway API specification. In particular, request headers are matched before request methods, when the specification describes that the request methods must be respected before headers are matched. This could result in unexpected behaviour with security This issue is fixed in Cilium v1.15.8 and v1.16.1. There is no workaround for this issue.
Published: 2024-08-15T20:26:53.455Z
Updated: 2024-08-15T20:46:34.910Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-42486 |
vulnerable | 2026-06-08 06:45:46.555388 |
Cilium vulnerable to information leakage via incorrect ReferenceGrant update logic in Gateway API
MEDIUM (5.4)
Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In versions on the 1.15.x branch prior to 1.15.8 and the 1.16.x branch prior to 1.16.1, ReferenceGrant changes are not correctly propagated in Cilium's GatewayAPI controller, which could lead to Gateway resources being able to access secrets for longer than intended, or to Routes having the ability to forward traffic to backends in other namespaces for longer than intended. This issue has been patched in Cilium v1.15.8 and v1.16.1. As a workaround, any modification of a related Gateway/HTTPRoute/GRPCRoute/TCPRoute CRD (for example, adding any label to any of these resources) will trigger a reconciliation of ReferenceGrants on an affected cluster.
Published: 2024-08-16T14:34:41.560Z
Updated: 2024-08-16T14:54:16.632Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.