CVE-2026-73549: envoyproxy envoy · Unchecked Error Condition
Affects envoyproxy envoySource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium · fixed in 1.39.1 : update envoyproxy envoy when convenient.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.39.1, 1.38.4, 1.37.6 +1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade envoy and envoyproxy/envoy to 1.39.1, 1.38.4, 1.37.6 or 1.36.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| envoyproxyenvoy | Affected
| Fixed in
|
| envoyproxyenvoy | Affected
| Fixed in
|
| envoyproxyenvoy | Affected
| Fixed in
|
| envoyproxyenvoy | Affected
| Fixed in
|
GitHubenvoyproxy/envoypkg:github/envoyproxy/envoyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in Envoy versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1. Users should upgrade to one of these versions or later to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-73549 is a medium severity vulnerability in Envoy proxy prior to versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1. It involves improper handling of scoped IPv6 addresses in certain network paths, which can cause the process to terminate unexpectedly due to exceptions or aborts. This affects deployments using kernel-provided scoped IPv6 destinations in ORIGINAL_DST transparent-proxy setups and certain QUIC connection paths. The issue is fixed in the specified versions.
References
- github.com/envoyproxy/envoy/security/advisories/GHSA-jp5f-qr64-c9vw (opens in a new tab)
- github.com/envoyproxy/envoy/commit/109e5a5b08ad10d99074cefd55a747a16ee64da7 (opens in a new tab)
- github.com/envoyproxy/envoy/commit/59b1744a6cb62746db418ac06fc5e359fd25fdb7 (opens in a new tab)
- github.com/envoyproxy/envoy/commit/6e39f4c94deff7a60d382c2d95883e0ea49ff691 (opens in a new tab)
- github.com/envoyproxy/envoy/commit/ab2dca2d65b079768230a7c3d825afeefa330215 (opens in a new tab)
- github.com/envoyproxy/envoy/releases/tag/v1.36.10 (opens in a new tab)
- github.com/envoyproxy/envoy/releases/tag/v1.37.6 (opens in a new tab)
- github.com/envoyproxy/envoy/releases/tag/v1.38.4 (opens in a new tab)
- github.com/envoyproxy/envoy/releases/tag/v1.39.1 (opens in a new tab)