CVE-2026-48497
Envoyproxy Envoy ≤ 1.35.13
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2026-48497 is a medium-severity Use of Incorrect Operator (CWE-480) vulnerability in Envoyproxy Envoy. Its CVSS base score is 5.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-39821
Vulnerability Data
Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.35.11, 1.36.7, 1.37.3, and 1.38.1, in cases where UDP DNS filter is configured with local resolution containing a name with the length of 255 octets…
more
or remote resolution for a name of 255 octets long can complete successfully, a query with such name will result in abnormal process termination. The abnormal process termination is triggered by an invalid runtime precondition that the query name is strictly less than 255 octets, contradicting DNS specification rfc1035#section-2.3.4 that the name can be 255 or less octets. This vulnerability is fixed in 1.35.11, 1.36.7, 1.37.3, and 1.38.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
DNS query of 255 octets triggers process crash in Envoy edge proxy (public-facing service), enabling remote DoS via application exploitation.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Enforces validation of DNS query name length to reject or safely handle 255-octet names before the failing precondition check.
Requires prompt application of the vendor patches (1.35.11+) that correct the incorrect length precondition in the UDP DNS filter.
Enables monitoring of Envoy process terminations or abnormal exits triggered by crafted 255-octet DNS queries.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices (reviews, static analysis, testing) directly catch incorrect-operator bugs while the weakness is only one narrow class of coding defect the control addresses.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing and code review can catch operator errors before release.
Secure coding standards and peer review directly prevent accidental use of incorrect operators.
Change management processes may include code review gates that incidentally catch operator mistakes.