CVE-2024-34363: envoyproxy envoy · Uncaught Exception
Affects envoyproxy envoySource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 5 Nov 2026, 16:20 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2024-06-21.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Jun 2024
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| envoyproxyenvoy | Affected
| Fixed in– |
AI-suggested
Until a fix is available, consider mitigating by validating or sanitizing downstream input to avoid incomplete UTF-8 strings or deploying Envoy versions outside the affected ranges.
Description
CVE-2024-34363 is a high-severity vulnerability in Envoy proxy versions 1.28.0 through 1.28.3, 1.29.0 through 1.29.4, and 1.30.0 through 1.30.1. It arises from how Envoy uses the nlohmann JSON library, which can throw an uncaught exception when processing incomplete UTF-8 strings from downstream data. This uncaught exception causes Envoy to crash, resulting in a denial of service.