CVE-2025-30162: Github.com/cilium/cilium Remote Code Execution Vulnerability

LOW
Advisory Identifier: GHSA-24qp-4xx8-3jvj
CVSS 3.2
CWE-863
Published
Advisory Summary

CVE-2025-30162 is a LOW (CVSS 3.2) remote code execution vulnerability (CWE-863: Incorrect Authorization) affecting Github.com/cilium/cilium libraries in the Go ecosystem. The issue involves cilium east-west traffic not subject to egress policy enforcement for requests via gateway api load balancers. Remediation is available by upgrading affected packages to version 1.16.8, 1.17.2, 1.15.15.

CVE-2025-30162 at a Glance

CVE Identifier CVE-2025-30162
GHSA Identifier GHSA-24qp-4xx8-3jvj
Severity LOW
CVSS v3.1 Base Score 3.2
CWE Classification CWE-863: Incorrect Authorization
Affected Product Github.com/cilium/cilium
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 3.2

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

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

How to Fix CVE-2025-30162

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.16.8
Upgrade github.com/cilium/cilium to 1.16.8
github.com/cilium/cilium fixed: 1.17.2
Upgrade github.com/cilium/cilium to 1.17.2
github.com/cilium/cilium fixed: 1.15.15
Upgrade github.com/cilium/cilium to 1.15.15
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-2025-30162, 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.16.8), 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-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. 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 For Cilium users who: - Use Gateway API for Ingress for some services **AND** - Use [LB-IPAM](https://docs.cilium.io/en/stable/network/lb-ipam/) or BGP for LB Service implementation **AND** - Use network policies to block egress traffic from workloads in a namespace to workloads in other namespaces Egress traffic from workloads covered by such network policies to LoadBalancers configured by `Gateway` resources will incorrectly be allowed. LoadBalancer resources not deployed via a Gateway API configuration are not affected by this issue. ### Patches This issue was fixed by https://github.com/cilium/proxy/pull/1172. This issue affects: - Cilium v1.15 between v1.15.0 and v1.15.14 inclusive - Cilium v1.16 between v1.16.0 and v1.16.7 inclusive - Cilium v1.17 between v1.17.0 and v1.17.1 inclusive This issue is fixed in: - Cilium v1.15.15 - Cilium v1.16.8 - Cilium v1.17.2 ### Workarounds A Clusterwide Cilium Network Policy can be used to work around this issue for users who are unable to upgrade. An outline of such a policy is provided below: ``` apiVersion: "cilium.io/v2" kind: CiliumClusterwideNetworkPolicy metadata: name: "workaround" spec: endpointSelector: matchExpressions: - key: reserved:ingress operator: Exists ingress: - fromEntities: - world ``` - The policy opens up connectivity from all locations outside the cluster into the Cilium Ingress Gateway. - The policy establishes a default deny for all other traffic towards the Cilium Ingress Gateway, including all in-cluster sources. - It is possible to tailor the policy to more narrowly allow inbound traffic while creating a default deny posture for traffic between namespaces. Users should edit the policy to bring it in line with the security requirements particular to their environments. ### Acknowledgements The Cilium community has worked together with members of the Isovalent team to prepare these mitigations. Special thanks to @jrajahalme for the fix. ### For more information If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [security@cilium.io](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.

CVE-2025-30162 Affected Github.com/cilium/cilium Versions

3 component(s)
Fixed Versions:
1.16.81.17.21.15.15
Product / Package Ecosystem Affected Versions Fixed Version
github.com/cilium/cilium
Go
≥ 1.16.0
< 1.16.8
1.16.8
github.com/cilium/cilium
Go
≥ 1.17.0
< 1.17.2
1.17.2
github.com/cilium/cilium
Go
≥ 1.15.0
< 1.15.15
1.15.15

References

Frequently Asked Questions

What is CVE-2025-30162?
CVE-2025-30162 is a security vulnerability in Github.com/cilium/cilium involving Cilium East-west traffic not subject to egress policy enforcement for requests via Gateway API load balancers under CWE-863: Incorrect Authorization.
Which Github.com/cilium/cilium versions are affected?
Affected versions include releases prior to 1.16.8, 1.17.2, 1.15.15 across affected packages: github.com/cilium/cilium.
What version fixes CVE-2025-30162?
Upgrading to 1.16.8, 1.17.2, 1.15.15 (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.16.8, 1.17.2, 1.15.15. Upgrade your dependency to 1.16.8, 1.17.2, 1.15.15 or later.
What is the CVSS score of CVE-2025-30162?
CVE-2025-30162 has a CVSS v3.1 base score of 3.2 (LOW) with vector string CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N.
What CWE is associated with CVE-2025-30162?
CVE-2025-30162 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check Go dependencies for CVE-2025-30162?
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-24qp-4xx8-3jvj",
  "modified" : "2025-03-24T21:47:14Z",
  "published" : "2025-03-24T19:05:04Z",
  "aliases" : [ "CVE-2025-30162" ],
  "summary" : "Cilium East-west traffic not subject to egress policy enforcement for requests via Gateway API load balancers",
  "details" : "### Impact\n\nFor Cilium users who:\n- Use Gateway API for Ingress for some services **AND**\n- Use [LB-IPAM](https://docs.cilium.io/en/stable/network/lb-ipam/) or BGP for LB Service implementation **AND**\n- Use network policies to block egress traffic from workloads in a namespace to workloads in other namespaces\n\nEgress traffic from workloads covered by such network policies to LoadBalancers configured by `Gateway` resources will incorrectly be allowed.\n\nLoadBalancer resources not deployed via a Gateway API configuration are not affected by this issue.\n\n### Patches\n\nThis issue was fixed by https://github.com/cilium/proxy/pull/1172.\n\nThis issue affects:\n\n- Cilium v1.15 between v1.15.0 and v1.15.14 inclusive\n- Cilium v1.16 between v1.16.0 and v1.16.7 inclusive\n- Cilium v1.17 between v1.17.0 and v1.17.1 inclusive\n\nThis issue is fixed in:\n\n- Cilium v1.15.15\n- Cilium v1.16.8\n- Cilium v1.17.2\n\n### Workarounds\n\nA Clusterwide Cilium Network Policy can be used to work around this issue for users who are unable to upgrade. An outline of such a policy is provided below:\n\n```\napiVersion: \"cilium.io/v2\"\nkind: CiliumClusterwideNetworkPolicy\nmetadata:\n  name: \"workaround\"\nspec:\n  endpointSelector:\n    matchExpressions:\n    - key: reserved:ingress\n      operator: Exists\n  ingress:\n  - fromEntities:\n    - world\n```\n\n- The policy opens up connectivity from all locations outside the cluster into the Cilium Ingress Gateway.\n- The policy establishes a default deny for all other traffic towards the Cilium Ingress Gateway, including all in-cluster sources.\n- It is possible to tailor the policy to more narrowly allow inbound traffic while creating a default deny posture for traffic between namespaces. Users should edit the policy to bring it in line with the security requirements particular to their environments.\n\n### Acknowledgements\n\nThe Cilium community has worked together with members of the Isovalent team to prepare these mitigations. Special thanks to @jrajahalme for the fix.\n\n### For more information\n\nIf you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [security@cilium.io](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/cilium/cilium"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.16.0"
      }, {
        "fixed" : "1.16.8"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/cilium/cilium"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.17.0"
      }, {
        "fixed" : "1.17.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/cilium/cilium"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.15.0"
      }, {
        "fixed" : "1.15.15"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/cilium/cilium/security/advisories/GHSA-24qp-4xx8-3jvj"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-30162"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/cilium/proxy/pull/1172"
  }, {
    "type" : "WEB",
    "url" : "https://docs.cilium.io/en/stable/network/lb-ipam"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/cilium/cilium"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-863" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-03-24T19:05:04Z",
    "nvd_published_at" : "2025-03-24T19:15:52Z"
  }
}