Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.17.14, 1.18.8, and 1.19.2, Ingress Network Policies are not enforced for traffic from pods to L7 Services (Envoy, GAMMA) with a local backend on the same node, when Per-Endpoint Routing is enabled and BPF Host Routing is disabled. Per-Endpoint Routing is disabled by default, but is automatically enabled in deployments using cloud IPAM, including Cilium ENI on EKS (eni.enabled), AlibabaCloud ENI (alibabacloud.enabled), Azure IPAM (azure.enabled, but not AKS BYOCNI), and some GKE deployments (gke.enabled; managed offerings such as GKE Dataplane V2 may use different defaults). It is typically not enabled in tunneled deployments, and chaining deployments are not affected. In practice, Amazon EKS with Cilium ENI mode is likely the most common affected environment. Versions 1.17.14, 1.18.8, and 1.19.2 contain a patch. There is currently no officially verified or comprehensive workaround for this issue. The only option would be to disable per-endpoint routes, but this will likely cause disruptions to ongoing connections, and potential conflicts if running in cloud providers.
CVE-2026-33726
This medium-severity CVE scores 4.3 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(low)
- EG Risk
- 24(Track)EG Risk 24/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 16%
- KEV
- Not listed
Published
March 27, 2026
Last Modified
June 17, 2026
References (6)
- security-advisories@githubhttps://docs.cilium.io/en/stable/network/concepts/routing/#routing
- security-advisories@githubhttps://docs.cilium.io/en/stable/network/kubernetes/policy/#network-policy
- security-advisories@githubhttps://docs.cilium.io/en/stable/network/servicemesh/l7-traffic-management
- security-advisories@githubhttps://docs.cilium.io/en/stable/operations/performance/tuning/#ebpf-host-routing
- security-advisories@githubhttps://github.com/cilium/cilium/pull/44693
- security-advisories@githubhttps://github.com/cilium/cilium/security/advisories/GHSA-hxv8-4j4r-cqgv
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:20 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-863 · CWE-284
Frequently asked(5)
What is CVE-2026-33726?
When was CVE-2026-33726 disclosed?
Is CVE-2026-33726 actively exploited?
What is the CVSS score of CVE-2026-33726?
How do I remediate CVE-2026-33726?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-33726
Is Your Infrastructure Affected by CVE-2026-33726?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.