CVE-2026-49445: Cilium: Sensitive information disclosure and cluster disruption via local Envoy admin socket access
Impact
When 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:
- Exposing TLS secrets - Disrupting traffic in the cluster - Terminating the Envoy process
This issue affects both the embedded and standalone Envoy deployment models.
Patches
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.14
This issue has been patched in https://github.com/cilium/cilium/pull/44512, included in:
- Cilium v1.19.2 - Cilium v1.18.8 - Cilium v1.17.14
Workarounds
There is no known workaround to this issue.
Acknowledgements
The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to moemen for reporting the issue and 0xch4z for their work on triaging and remediating this issue.
For more information
If there are any questions or comments about this advisory, please reach out on [Slack (https://docs.cilium.io/en/latest/community/community/).
If 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. This is a private mailing list for the Cilium security team, and the report will be treated as a top priority.
Other sources
Cilium is a networking, observability, and security solution. Prior to 1.17.14, 1.18.8, and 1.19.2, when Cilium L7 functionality is enabled, the embedded or standalone Envoy instance creates a world-accessible admin.sock on cluster nodes, allowing a local attacker to access Envoy admin endpoints, expose TLS secrets, disrupt cluster traffic, or terminate Envoy. This issue is fixed in versions 1.17.14, 1.18.8, and 1.19.2.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/cilium/ciliumto a version that resolves this vulnerability.Fixed in 1.17.14 - Upgrade
Upgrade
go/github.com/cilium/ciliumto a version that resolves this vulnerability.Fixed in 1.18.8 - Upgrade
Upgrade
go/github.com/cilium/ciliumto a version that resolves this vulnerability.Fixed in 1.19.2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.17.14 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.18.8 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.19.2
Event History
Frequently Asked Questions
What is the severity of CVE-2026-49445?
The severity of CVE-2026-49445 is rated as critical with a score of 9.2.
What is the impact of CVE-2026-49445?
CVE-2026-49445 allows local attackers to access sensitive Envoy admin endpoints through a world-accessible socket created on cluster nodes.
How do I fix CVE-2026-49445?
To fix CVE-2026-49445, ensure that the Cilium L7 functionality is properly configured to restrict access to the Envoy admin endpoints.
Who is affected by CVE-2026-49445?
CVE-2026-49445 affects any deployments utilizing Cilium with L7 functionality enabled on their cluster.
What versions of Cilium are vulnerable to CVE-2026-49445?
CVE-2026-49445 impacts versions of Cilium that enable the L7 functionality, though specific version details should be reviewed in the advisories.