{ "document": { "category": "csaf_base", "csaf_version": "2.0", "distribution": { "tlp": { "label": "WHITE" } }, "lang": "en", "notes": [ { "category": "legal_disclaimer", "text": "The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this portal to enhance access to its information and vulnerabilities. The use of this information is subject to the following terms and conditions:\n\nThe vulnerabilities disclosed in this portal are gathered by NCSC-NL from a variety of open sources, which the user can retrieve from other platforms. NCSC-NL makes every reasonable effort to ensure that the content of this portal is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or real-time keeping up-to-date. NCSC-NL does not control nor guarantee the accuracy, relevance, timeliness or completeness of information obtained from these external sources. The vulnerabilities disclosed in this portal are intended solely for the convenience of professional parties to take appropriate measures to manage the risks posed to the cybersecurity. No rights can be derived from the information provided therein.\n\nNCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of the vulnerabilities disclosed in this portal. This includes damage resulting from the inaccuracy of incompleteness of the information contained in it.\nThe information on this page is subject to Dutch law. All disputes related to or arising from the use of this portal regarding the disclosure of vulnerabilities will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings." } ], "publisher": { "category": "coordinator", "contact_details": "cert@ncsc.nl", "name": "National Cyber Security Centre", "namespace": "https://www.ncsc.nl/" }, "title": "CVE-2026-33726", "tracking": { "current_release_date": "2026-04-01T18:28:14.976960Z", "generator": { "date": "2026-02-17T15:00:00Z", "engine": { "name": "V.E.L.M.A", "version": "1.7" } }, "id": "CVE-2026-33726", "initial_release_date": "2026-03-26T17:40:59.442833Z", "revision_history": [ { "date": "2026-03-26T17:40:59.442833Z", "number": "1", "summary": "CVE created.| Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (7).| CWES updated (1)." }, { "date": "2026-03-26T17:41:11.018469Z", "number": "2", "summary": "NCSC Score created." }, { "date": "2026-03-26T18:12:37.391519Z", "number": "3", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (3).| References created (6).| CWES updated (1)." }, { "date": "2026-03-26T18:12:45.657549Z", "number": "4", "summary": "NCSC Score updated." }, { "date": "2026-03-27T00:14:03.190385Z", "number": "5", "summary": "Source created.| CVE status created. (valid)| Description created for source.| References created (6)." }, { "date": "2026-03-27T00:38:38.639611Z", "number": "6", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (1).| Products connected (2).| References created (6).| CWES updated (1)." }, { "date": "2026-03-27T00:38:49.411783Z", "number": "7", "summary": "NCSC Score updated." }, { "date": "2026-03-27T01:25:06.885232Z", "number": "8", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (6).| CWES updated (1)." }, { "date": "2026-03-27T01:25:08.664087Z", "number": "9", "summary": "NCSC Score updated." }, { "date": "2026-03-27T07:35:00.733907Z", "number": "10", "summary": "NCSC Score updated." }, { "date": "2026-03-27T19:44:27.046784Z", "number": "11", "summary": "Unknown change." }, { "date": "2026-03-27T20:56:22.592807Z", "number": "12", "summary": "Source connected.| CVE status created. (valid)| EPSS created." }, { "date": "2026-03-28T07:57:19.856332Z", "number": "13", "summary": "References created (1)." }, { "date": "2026-04-01T18:28:05.214697Z", "number": "14", "summary": "Products connected (3).| Product Identifiers created (3)." }, { "date": "2026-04-01T18:28:07.034446Z", "number": "15", "summary": "NCSC Score updated." } ], "status": "interim", "version": "15" } }, "product_tree": { "branches": [ { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:unknown/<1.17.14", "product": { "name": "vers:unknown/<1.17.14", "product_id": "CSAFPID-5920661", "product_identification_helper": { "cpe": "cpe:2.3:a:cilium:cilium:*:*:*:*:*:*:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/>=0|<1.17.14", "product": { "name": "vers:unknown/>=0|<1.17.14", "product_id": "CSAFPID-5918523" } }, { "category": "product_version_range", "name": "vers:unknown/>=1.18.0|<1.18.8", "product": { "name": "vers:unknown/>=1.18.0|<1.18.8", "product_id": "CSAFPID-5918524", "product_identification_helper": { "cpe": "cpe:2.3:a:cilium:cilium:*:*:*:*:*:*:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/>=1.19.0|<1.19.2", "product": { "name": "vers:unknown/>=1.19.0|<1.19.2", "product_id": "CSAFPID-5918525", "product_identification_helper": { "cpe": "cpe:2.3:a:cilium:cilium:*:*:*:*:*:*:*:*" } } } ], "category": "product_name", "name": "Cilium" } ], "category": "vendor", "name": "Cilium" } ] }, "vulnerabilities": [ { "cve": "CVE-2026-33726", "cwe": { "id": "CWE-863", "name": "Incorrect Authorization" }, "notes": [ { "category": "description", "text": "### Impact\n\nIngress [Network Policies](https://docs.cilium.io/en/stable/network/kubernetes/policy/#network-policy) are not enforced for traffic from pods to L7 Services ([Envoy](https://docs.cilium.io/en/stable/network/servicemesh/l7-traffic-management), GAMMA) with a local backend on the same node, when [Per-Endpoint Routing](https://docs.cilium.io/en/stable/network/concepts/routing/#routing) is enabled and [BPF Host Routing](https://docs.cilium.io/en/stable/operations/performance/tuning/#ebpf-host-routing) is disabled.\n\nPer-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.\n\n### Patches\n\nThis issue was fixed by #44693.\n\nThis issue affects:\n\n* Cilium v1.19 between v1.19.0 and v1.19.1 inclusive\n* Cilium v1.18 between v1.18.0 and v1.18.7 inclusive\n* All versions of Cilium prior to v1.17.13\n\nThis issue is fixed in:\n\n* Cilium v1.19.2\n* Cilium v1.18.8\n* Cilium v1.17.14\n\n### Workarounds\n\nDisclaimer: 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.\n\n### Acknowledgements\n\nThe Cilium community has worked together with members of the Northflank and Isovalent teams to prepare these mitigations. Cilium thanks @sudeephb and @Champ-Goblem for reporting the issue and to @smagnani96 and @julianwiedmann for helping with the resolution.\n\n### For more information\n\nAnyone who believes a vulnerability affecting Cilium has been found is strongly encouraged to report it to the security mailing list at security@cilium.io. This is a private mailing list for the Cilium security team, and any such report will be treated as top priority. Please also address any comments or questions on this advisory to the same mailing list.", "title": "github - https://api.github.com/advisories/GHSA-hxv8-4j4r-cqgv" }, { "category": "description", "text": "### Impact\n\nIngress [Network Policies](https://docs.cilium.io/en/stable/network/kubernetes/policy/#network-policy) are not enforced for traffic from pods to L7 Services ([Envoy](https://docs.cilium.io/en/stable/network/servicemesh/l7-traffic-management), GAMMA) with a local backend on the same node, when [Per-Endpoint Routing](https://docs.cilium.io/en/stable/network/concepts/routing/#routing) is enabled and [BPF Host Routing](https://docs.cilium.io/en/stable/operations/performance/tuning/#ebpf-host-routing) is disabled.\n\nPer-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.\n\n### Patches\n\nThis issue was fixed by #44693.\n\nThis issue affects:\n\n* Cilium v1.19 between v1.19.0 and v1.19.1 inclusive\n* Cilium v1.18 between v1.18.0 and v1.18.7 inclusive\n* All versions of Cilium prior to v1.17.13\n\nThis issue is fixed in:\n\n* Cilium v1.19.2\n* Cilium v1.18.8\n* Cilium v1.17.14\n\n### Workarounds\n\nDisclaimer: 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.\n\n### Acknowledgements\n\nThe Cilium community has worked together with members of the Northflank and Isovalent teams to prepare these mitigations. Cilium thanks @sudeephb and @Champ-Goblem for reporting the issue and to @smagnani96 and @julianwiedmann for helping with the resolution.\n\n### For more information\n\nAnyone who believes a vulnerability affecting Cilium has been found is strongly encouraged to report it to the security mailing list at security@cilium.io. This is a private mailing list for the Cilium security team, and any such report will be treated as top priority. Please also address any comments or questions on this advisory to the same mailing list.", "title": "osv - https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGHSA-hxv8-4j4r-cqgv.json?alt=media" }, { "category": "description", "text": "Cilium L7 proxy may bypass Kubernetes NetworkPolicy for same-node traffic in github.com/cilium/cilium", "title": "osv - https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGO-2026-4856.json?alt=media" }, { "category": "description", "text": "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.", "title": "cveprojectv5 - https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/33xxx/CVE-2026-33726.json" }, { "category": "description", "text": "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.", "title": "nvd - https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-33726" }, { "category": "other", "text": "6e-05", "title": "EPSS" }, { "category": "other", "text": "5.0", "title": "NCSC Score" }, { "category": "other", "text": "Is related to CWE-863 (Incorrect Authorization), There is product data available from source Nvd", "title": "NCSC Score top increasing factors" }, { "category": "other", "text": "Is related to (a version of) an uncommon product, There is cwe data available from source Github", "title": "NCSC Score top decreasing factors" } ], "product_status": { "known_affected": [ "CSAFPID-5918523", "CSAFPID-5918524", "CSAFPID-5918525", "CSAFPID-5920661" ] }, "references": [ { "category": "external", "summary": "Source - github", "url": "https://api.github.com/advisories/GHSA-hxv8-4j4r-cqgv" }, { "category": "external", "summary": "Source - osv", "url": "https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGHSA-hxv8-4j4r-cqgv.json?alt=media" }, { "category": "external", "summary": "Source - osv", "url": "https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/Go%2FGO-2026-4856.json?alt=media" }, { "category": "external", "summary": "Source - cveprojectv5", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/33xxx/CVE-2026-33726.json" }, { "category": "external", "summary": "Source - nvd", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-33726" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://github.com/cilium/cilium/security/advisories/GHSA-hxv8-4j4r-cqgv" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://github.com/cilium/cilium/pull/44693" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://docs.cilium.io/en/stable/network/concepts/routing/#routing" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://docs.cilium.io/en/stable/network/kubernetes/policy/#network-policy" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://docs.cilium.io/en/stable/network/servicemesh/l7-traffic-management" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://docs.cilium.io/en/stable/operations/performance/tuning/#ebpf-host-routing" }, { "category": "external", "summary": "Reference - github", "url": "https://github.com/advisories/GHSA-hxv8-4j4r-cqgv" }, { "category": "external", "summary": "Reference - github", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33726" } ], "scores": [ { "cvss_v3": { "version": "3.1", "vectorString": "CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N", "baseScore": 5.4, "baseSeverity": "MEDIUM" }, "products": [ "CSAFPID-5918523", "CSAFPID-5918524", "CSAFPID-5918525", "CSAFPID-5920661" ] } ], "title": "CVE-2026-33726" } ] }