{"id":"CVE-2026-49445","aliases":["GHSA-3fcv-jvfp-m4q9"],"title":"Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access","summary":"Cilium vulnerable to sensitive information disclosure and cluster disruption via local Envoy admin socket access","severity":"critical","cvss":9.2,"cwe":["CWE-862"],"vendor":"cilium","product":"github.com/cilium/cilium","ecosystem":"go","affected":["github.com/cilium/cilium >= 1.19.0, < 1.19.2","github.com/cilium/cilium >= 1.18.0, < 1.18.8","github.com/cilium/cilium < 1.17.14"],"patched":["github.com/cilium/cilium 1.19.2","github.com/cilium/cilium 1.18.8","github.com/cilium/cilium 1.17.14"],"published":"2026-07-06","updated":"2026-07-06","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-3fcv-jvfp-m4q9","references":[{"url":"https://github.com/cilium/cilium/security/advisories/GHSA-3fcv-jvfp-m4q9"},{"url":"https://github.com/cilium/cilium/pull/44512"},{"url":"https://github.com/advisories/GHSA-3fcv-jvfp-m4q9"}],"tags":["ghsa","go"],"ingestedAt":"2026-07-06T17:44:51.401Z","epss":0.00166,"epssPercentile":0.06226,"slug":"CVE-2026-49445","body":"## Overview\n\n### Impact\n\nWhen Cilium L7 functionality is enabled on a cluster, the Envoy instance supporting this functionality creates a world-accessible socket on cluster nodes. A local attacker would be able to access Envoy admin endpoints. Depending on deployment configuration, this can expose sensitive information or allow disruptive administrative operations, such as:\n\n- Exposing TLS secrets\n- Disrupting traffic in the cluster\n- Terminating the Envoy process  \n\nThis issue affects both the embedded and standalone Envoy deployment models.\n\n### Patches\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.14\n\nThis issue has been patched in https://github.com/cilium/cilium/pull/44512, included in:\n\n- Cilium v1.19.2\n- Cilium v1.18.8\n- Cilium v1.17.14\n\n### Workarounds\n\nThere is no known workaround to this issue.\n\n### Acknowledgements\n\nThe Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to [moemen](https://github.com/moemen) for reporting the issue and [0xch4z](https://github.com/0xch4z) for their work on triaging and remediating this issue.\n\n### For more information\n\nIf there are any questions or comments about this advisory, please reach out on [Slack (https://docs.cilium.io/en/latest/community/community/).\n\nIf anyone thinks they have found a vulnerability affecting Cilium, it is strongly encouraged to report it to the security mailing list at [security@cilium.io](mailto:security@cilium.io). This is a private mailing list for the Cilium security team, and the report will be treated as a top priority.\n\n## Affected packages\n\n- `github.com/cilium/cilium >= 1.19.0, < 1.19.2`\n- `github.com/cilium/cilium >= 1.18.0, < 1.18.8`\n- `github.com/cilium/cilium < 1.17.14`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `github.com/cilium/cilium 1.19.2`\n- `github.com/cilium/cilium 1.18.8`\n- `github.com/cilium/cilium 1.17.14`","depth":"midnight","depthScore":51,"depthScoreParts":{"impact":50.6,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}