Service crash via unbounded HTTP/2 header continuation
Published Apr 4, 2024 · Updated Nov 4, 2025
Denial of service in Envoy 1.29.0 through 1.29.1 allows remote attackers to exhaust memory via HTTP/2 CONTINUATION frames. The HTTP/2 codec fails to reset a request after header-map limits are exceeded, so frames lacking END_HEADERS retain unbounded header state. An unauthenticated HTTP/2 peer can drive memory growth until the Envoy process terminates, interrupting proxied traffic.
Summary
What happened
Denial of service in Envoy 1.29.0 through 1.29.1 allows remote attackers to exhaust memory via HTTP/2 CONTINUATION frames. The HTTP/2 codec fails to reset a request after header-map limits are exceeded, so frames lacking END_HEADERS retain unbounded header state. An unauthenticated HTTP/2 peer can drive memory growth until the Envoy process terminates, interrupting proxied traffic.
The record
- CVE
- CVE-2024-27919
- Published
- Apr 4, 2024
- Updated
- Nov 4, 2025
- Vendor
- Envoy Proxy
- Product
- Envoy
- Classifications
- CWE-390, T1499.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.29.0, < 1.29.2
- Affected versionversion=1.29.0 <1.29.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo