How severe is CVE-2026-49445?

CVE-2026-49445 has a CVSS score of 9.2/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-49445?

CVE-2026-49445 affects the following packages: github.com/cilium/cilium (Go), github.com/cilium/cilium (Go), github.com/cilium/cilium (Go). Ecosystems affected: Go.

How do I fix CVE-2026-49445?

Update github.com/cilium/cilium to 1.19.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-49445 is resolved across your whole dependency graph.

How do I detect CVE-2026-49445 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cilium/cilium, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-49445 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-49445 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-49445 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-49445?

CVE-2026-49445 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 5th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-49445?

CVE-2026-49445 is classified as CWE-732 (CWE-732). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-49445 published, and has it been updated?

CVE-2026-49445 was published on July 15, 2026 and was last updated on August 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

CRITICAL severity

CVE-2026-49445 — cilium

CRITICALFix: cilium/cilium@7bfbdd5

CVE-2026-49445 is a critical-severity (CVSS 9.2) CWE-732 vulnerability in github.com/cilium/cilium. A fix is available for github.com/cilium/cilium — see the affected versions and patch details below.

Cilium: Sensitive information disclosure and cluster disruption via local Envoy admin socket access

Also known asBIT-cilium-2026-49445BIT-cilium-operator-2026-49445BIT-hubble-relay-2026-49445GHSA-3fcv-jvfp-m4q9GO-2026-5905

Published

Jul 15, 2026

Updated

Aug 16, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 14, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-49445.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs5th percentile — riskier than 5% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-49445 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 388,997 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

🐹github.com/cilium/cilium🐹github.com/cilium/cilium🐹github.com/cilium/cilium

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 [email protected]. This is a private mailing list for the Cilium security team, and the report will be treated as a top priority.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/cilium/cilium`	≥ 1.19.0&&< 1.19.2	1.19.2`go get github.com/cilium/cilium@v1.19.2`
🐹Go	`github.com/cilium/cilium`	≥ 1.18.0&&< 1.18.8	1.18.8`go get github.com/cilium/cilium@v1.18.8`
🐹Go	`github.com/cilium/cilium`	all versions	1.17.14`go get github.com/cilium/cilium@v1.17.14`

Affected Products

1 product · 3 configurations

Application

ciliumcilium

≥ 1.19.0 && < 1.19.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cilium/cilium, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/cilium/cilium to 1.19.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-49445 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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.