vciy

Cilium, incorrect authorization: 5 records, one defect family

Cilium has been reported 5 separate times for the same kind of mistake, CWE-863, between 2025-03-24 and 2026-07-15. A defect family is our own grouping of the CVE corpus: every record naming one product and one weakness class, collected so a repeat is visible as a repeat. No public source publishes this, and what this page counts is how often this one product has gone wrong in this one way.

What this page is, and what it is not

The records are public. This grouping is not. No source publishes defect families, so we built them: every record in the corpus sorted by the product an authority named and the weakness class carried with it, 21316 families over 105586 records. This one holds every record that names Cilium and carries CWE-863, matched character for character. We show the join because a grouping you cannot check is a grouping you should not cite.

That is 5 filings, between 2025-03-24 and 2026-07-15, landing on the same weakness class in the same product. At this count it is a repeat rather than a pattern, and the roster below is short enough to read in full. This is what we held on 2026-09-20.

A repeat is evidence about where to look. If you are reviewing Cilium, the records below say which mistake has already been found more than once, which is the cheapest place a reviewer can start. If you are asking the vendor a question, a count under one weakness class is a better question than any single record is.

What this page cannot tell you is decided by what was joined. A product name and a weakness class settled membership, so those two values are the whole of what the page asserts. Records here may sit in the same line of code or in unrelated parts of the product, and we hold no value that separates those cases. A fixed version named in one record closes that record and says nothing about the others. And nothing here describes anyone's systems, because no value in this family connects a product name to an installation.

20252026CVE-2025-30162, published 2025-03-24CVE-2025-30163, published 2025-03-24CVE-2026-26963, published 2026-02-19CVE-2026-53935, published 2026-07-07CVE-2026-56743, published 2026-07-15
3 of the 5 were published in 2026, and the rest are spread over 1.3 years, so this is one concentrated year with a tail rather than a steady rate.

The names the authorities used

One spelling, used by every authority that filed one of these records: cilium.

Family membership: held values. Joined on the product and weakness class the assigning authorities wrote, with no model involved.

What the records offer

No record in this family publishes a fixed version in held sources.

The earliest was published 2025-03-24 and the latest 2026-07-15. That span is how long this product kept producing this weakness, not how long any one record took to fix.

What this page does not cover

This is a family of records that read alike. It is not a shared vulnerability, not an inventory, and not a statement that one fix closes the rest. Each record's own state, its own dates and its own receipts are on its own page.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Everything this vendor has, including records outside this family:

CVE-2025-30162East-west traffic not subject to egress policy enforcement for requests via Gateway API load balancersCWE-863: Incorrect Authorization
CVE-2025-30163Node based network policies may incorrectly allow workload trafficCWE-863: Incorrect Authorization
CVE-2026-26963Cilium may not enforce host firewall policies when Native Routing, WireGuard and Node Encryption are enabledCWE-863: Incorrect Authorization
CVE-2026-53935CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service…CWE-863: Incorrect Authorization
CVE-2026-56743Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured…CWE-863: Incorrect Authorization

5 records, read from the index as it stood on 20 Sep 2026. Every row opens the record it names, and every value on that record opens its own receipt.

Everything on this page is free. Public data. Withholding it protects nothing.