CVE-2026-33726: Github.com/cilium/cilium Cilium L7 Proxy May Bypass Vulnerability

MODERATE
Advisory Identifier: GHSA-hxv8-4j4r-cqgv
CVSS 5.4
CWE-284 CWE-863
Published
Advisory Summary

CVE-2026-33726 is a MODERATE (CVSS 5.4) cilium l7 proxy may bypass vulnerability (CWE-284: Improper Access Control) affecting Github.com/cilium/cilium libraries in the Go ecosystem. The issue involves cilium l7 proxy may bypass kubernetes networkpolicy for same-node traffic. Remediation is available by upgrading affected packages to version 1.17.14, 1.18.8, 1.19.2.

CVE-2026-33726 at a Glance

CVE Identifier CVE-2026-33726
GHSA Identifier GHSA-hxv8-4j4r-cqgv
Severity MODERATE
CVSS v3.1 Base Score 5.4
CWE Classification CWE-284: Improper Access Control
Affected Product Github.com/cilium/cilium
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N).

Attack Vector Adjacent (AV:A)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-33726

To remediate this vulnerability, upgrade all affected Github.com/cilium/cilium dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/cilium/cilium fixed: 1.17.14
Upgrade github.com/cilium/cilium to 1.17.14
github.com/cilium/cilium fixed: 1.18.8
Upgrade github.com/cilium/cilium to 1.18.8
github.com/cilium/cilium fixed: 1.19.2
Upgrade github.com/cilium/cilium to 1.19.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/cilium/cilium

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-33726, inspect your project dependencies for Github.com/cilium/cilium:

inspect dependencies for github.com/cilium/cilium

Analyze the terminal output to locate any version of Github.com/cilium/cilium in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.17.14), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. In Github.com/cilium/cilium, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Ingress [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. 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. ### Patches This issue was fixed by #44693. This issue affects: * Cilium v1.19 between v1.19.0 and v1.19.1 inclusive * Cilium v1.18 between v1.18.0 and v1.18.7 inclusive * All versions of Cilium prior to v1.17.13 This issue is fixed in: * Cilium v1.19.2 * Cilium v1.18.8 * Cilium v1.17.14 ### Workarounds Disclaimer: 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. ### Acknowledgements The 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. ### For more information Anyone 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.

CVE-2026-33726 Affected Github.com/cilium/cilium Versions

3 component(s)
Fixed Versions:
1.17.141.18.81.19.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/cilium/cilium
Go
< 1.17.14
1.17.14
github.com/cilium/cilium
Go
≥ 1.18.0
< 1.18.8
1.18.8
github.com/cilium/cilium
Go
≥ 1.19.0
< 1.19.2
1.19.2

References

Frequently Asked Questions

What is CVE-2026-33726?
CVE-2026-33726 is a security vulnerability in Github.com/cilium/cilium involving Cilium L7 proxy may bypass Kubernetes NetworkPolicy for same-node traffic under CWE-284: Improper Access Control.
Which Github.com/cilium/cilium versions are affected?
Affected versions include releases prior to 1.17.14, 1.18.8, 1.19.2 across affected packages: github.com/cilium/cilium.
What version fixes CVE-2026-33726?
Upgrading to 1.17.14, 1.18.8, 1.19.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/cilium/cilium affected?
Yes, github.com/cilium/cilium is affected in releases prior to 1.17.14, 1.18.8, 1.19.2. Upgrade your dependency to 1.17.14, 1.18.8, 1.19.2 or later.
What is the CVSS score of CVE-2026-33726?
CVE-2026-33726 has a CVSS v3.1 base score of 5.4 (MODERATE) with vector string CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N.
What CWE is associated with CVE-2026-33726?
CVE-2026-33726 is classified under CWE-284: Improper Access Control (The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.).
How can I check Go dependencies for CVE-2026-33726?
Run the dependency tree command: 'inspect dependencies for github.com/cilium/cilium'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hxv8-4j4r-cqgv",
  "modified" : "2026-03-27T21:28:48Z",
  "published" : "2026-03-26T16:48:31Z",
  "aliases" : [ "CVE-2026-33726" ],
  "summary" : "Cilium L7 proxy may bypass Kubernetes NetworkPolicy for same-node traffic",
  "details" : "### 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/cilium/cilium"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.17.14"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/cilium/cilium"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.18.0"
      }, {
        "fixed" : "1.18.8"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/cilium/cilium"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.19.0"
      }, {
        "fixed" : "1.19.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/cilium/cilium/security/advisories/GHSA-hxv8-4j4r-cqgv"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33726"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/cilium/cilium/pull/44693"
  }, {
    "type" : "WEB",
    "url" : "https://docs.cilium.io/en/stable/network/concepts/routing/#routing"
  }, {
    "type" : "WEB",
    "url" : "https://docs.cilium.io/en/stable/network/kubernetes/policy/#network-policy"
  }, {
    "type" : "WEB",
    "url" : "https://docs.cilium.io/en/stable/network/servicemesh/l7-traffic-management"
  }, {
    "type" : "WEB",
    "url" : "https://docs.cilium.io/en/stable/operations/performance/tuning/#ebpf-host-routing"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/cilium/cilium"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-284", "CWE-863" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-26T16:48:31Z",
    "nvd_published_at" : "2026-03-27T01:16:20Z"
  }
}