CVE-2026-48042
Envoyproxy Envoy 1.18.0 – 1.35.13
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2026-48042 is a high-severity Excessively Deep Nesting (CWE-1124) vulnerability in Envoyproxy Envoy. Its CVSS base score is 7.5 (High).
Operationally, ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-39819
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, destructor of JSON Object results in stack overflow when deeply O(100K) nested objects are present. This vulnerability is fixed in…
more
1.35.11, 1.36.7, 1.37.3, and 1.38.1.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation activities can identify overly complex code structures that exceed acceptable nesting thresholds.
Requiring documented development standards and tools can enforce explicit limits on code complexity metrics including nesting depth.
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 include static analysis and code review rules that directly limit excessive nesting depth.
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.
Secure development life cycle mandates code reviews and design rules that can catch or prevent excessive nesting.
Secure system architecture and engineering principles include maintainability and complexity limits that address deep nesting.
Secure coding standards explicitly forbid or limit excessive nesting to improve readability and reduce defects.
Security testing can detect overly complex code but does not itself prevent the weakness.