Memory corruption via reentrant HTTP/2 scratch buffer
Published Oct 1, 2026 · Updated Oct 1, 2026
Use-after-free in Apache HTTP Server 2.4.0 through 2.4.68 allows remote attackers to corrupt server memory through HTTP/2 traffic. In mod_http2, reentrant processing reuses the shared session->bbtmp buffer; Apache identifies this as the use-after-free and wild-write path but does not publish the exact trigger sequence. Exposure requires mod_http2 and HTTP/2 to be enabled, and the published record does not establish code execution.
Summary
What happened
Use-after-free in Apache HTTP Server 2.4.0 through 2.4.68 allows remote attackers to corrupt server memory through HTTP/2 traffic. In mod_http2, reentrant processing reuses the shared session->bbtmp buffer; Apache identifies this as the use-after-free and wild-write path but does not publish the exact trigger sequence. Exposure requires mod_http2 and HTTP/2 to be enabled, and the published record does not establish code execution.
The record
- CVE
- CVE-2026-57941
- Published
- Oct 1, 2026
- Updated
- Oct 1, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache HTTP Server
- Classifications
- CWE-416, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 1, 2026CVE publishedPublication date reported by the CVE source.
- Oct 1, 2026Record 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=2.4.0 <=2.4.68
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started