CVE-2026-73549 — Improper Check for Unusual or Exceptional Conditions in Envoyproxy Envoy
Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1, Envoy's Utility::copyInternetAddressAndPort and QUIC client-address paths reconstruct scoped IPv6 addresses through addressAsString and Ipv6Instance. The string includes a percent scope identifier that inet_pton cannot parse, causing an exception or abort. Kernel-provided scoped IPv6 destinations in ORIGINAL_DST transparent-proxy deployments, and affected QUIC connection paths, can therefore terminate the process. The relevant scope boundary is that the HTTP use_http_header override rejects scoped addresses earlier; the advisory's crash path requires a kernel-provided original destination or the affected QUIC path. This issue is fixed in versions 1.36.10, 1.37.6, 1.38.4, and 1.39.1.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented mitigation — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Envoyproxy Envoy).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Envoyproxy | Envoy | < 1.36.10≥ 1.37.0 and < 1.37.6≥ 1.38.0 and < 1.38.4≥ 1.39.0 and < 1.39.1 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.3 | CVSS 3.1 | Medium | 1.6 | 3.6 | security-advisories@github.com via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: security-advisories@github.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CWE-754 · Improper Check for Unusual or Exceptional Conditions
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Fix documented
- CVSS changed · 5.3
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
9 on the record
- github.com/envoyproxy/envoy/security/advisories/GHSA-jp5f-qr64-c9vw
- github.com/envoyproxy/envoy/commit/6e39f4c94deff7a60d382c2d95883e0ea49ff691
- github.com/envoyproxy/envoy/commit/59b1744a6cb62746db418ac06fc5e359fd25fdb7
- github.com/envoyproxy/envoy/commit/109e5a5b08ad10d99074cefd55a747a16ee64da7
- github.com/envoyproxy/envoy/commit/ab2dca2d65b079768230a7c3d825afeefa330215
- github.com/envoyproxy/envoy/releases/tag/v1.38.4
- github.com/envoyproxy/envoy/releases/tag/v1.39.1
- github.com/envoyproxy/envoy/releases/tag/v1.37.6
- github.com/envoyproxy/envoy/releases/tag/v1.36.10
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-73553 Envoy is an open source edge and service proxy designed for cloud-native applications… 24d
- Medium CVE-2026-73511 Envoy is an open source edge and service proxy designed for cloud-native applications… 24d
- Medium CVE-2026-73551 Envoy is an open source edge and service proxy designed for cloud-native applications… 24d
- High CVE-2026-73548 HTTP Request Smuggling in Envoyproxy Envoy 24d
- High CVE-2026-73552 Improper Input Validation in Envoyproxy Envoy 24d
- High CVE-2026-73546 Cross-site Scripting (XSS) in Envoyproxy Envoy 24d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-73549 is "Improper Check for Unusual or Exceptional Conditions in Envoyproxy Envoy", rated Medium. It affects Envoy (Envoyproxy); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.