ApplicationsCritical 9.8Patch available
CVE-2026-57941
Use-after-free in Apache mod_http2 enabling RCE or DoS
How scary is it?
updated 16 Oct 2026- Yes
Works without logging in1
No account and no user action needed (CVSS PR:N, UI:N).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- None known
Public exploit code is out
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- None known
Attacks seen in the wild1
None reported that we know of. CISA's SSVC assessment says exploitation: none.
- No
On CISA's exploited list2
Not in the catalog as of our last sync.
Scare-o-meter
Act this week
Serious and within reach of attackers. Schedule the fix this week.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: Reachable over the network with no login and no user action; CVSS 9.8.1 Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run Apache Software Foundation Apache HTTP Server in an affected version>= 2.4.0 and <= 2.4.68
The CVE record states no fixed release.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per our analysisA patch is available
The CVE record we hold states no fixed release number. See the advisories in the references.
Recommendation, AI-writtenUpgrade to vendor-fixed Apache httpd release immediately; if not possible, disable HTTP/2 and apply WAF filters.
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
Major vulnerability. Apache HTTP Server is ubiquitous; a 9.8 use-after-free in mod_http2 can enable RCE or widespread DoS, impacting internet-facing web infrastructure.
- CVSS
- 9.8Criticalscored by CISA
- Exploited in the wild
- Not knownnot in CISA KEV as of our last sync
- EPSS
- 0.65%chance of exploitation in the next 30 daystop 49% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 1 Oct 2026analysed here 2 Oct 2026
Summary
Impact
Remote code execution or server crash via crafted HTTP/2 requests exploiting a use-after-free in mod_http2.
Triage
Executive summary (AI-written)
CVE-2026-57941 presents a critical vulnerability in the Apache HTTP Server, rated with a CVSS score of 9.8, indicating a significant risk for organizations relying on this software for their web infrastructure. This vulnerability allows remote code execution (RCE) or denial of service (DoS) through crafted HTTP/2 requests, enabled by a use-after-free condition in the mod_http2 module. Given the widespread use of the Apache HTTP Server across various industries, the potential business impact is severe, as exploitation could lead to unauthorized access or service disruptions.
Technical analysis (AI-written)
CVE-2026-57941 is a use-after-free vulnerability found in the mod_http2 module of Apache HTTP Server versions 2.4.0 through 2.4.68. With a high CVSS score of 9.8, it poses a substantial threat by allowing remote attackers to execute arbitrary code or crash the server via maliciously crafted HTTP/2 requests. The use-after-free flaw occurs when an application continues to access a memory location after it has been freed, creating an opportunity for an adversary to manipulate the program's flow and execute code in the context of the affected server process. Exploitation of this vulnerability can be achieved without requiring advanced skills due to the nature of HTTP/2 requests, making it accessible for opportunistic attackers. This highlights the critical need for prompt remediation, as attackers may leverage automated tools to scan and target vulnerable systems. Additionally, the potential for service disruption through DoS attacks means that organizations could face downtime, negatively impacting their operations and customer trust. Immediate action is highly recommended; organizations should upgrade to the latest vendor-fixed release of Apache HTTP Server. For those unable to apply the update immediately, mitigation strategies include disabling the HTTP/2 protocol in the server configuration and implementing Web Application Firewalls (WAF) to filter out malicious traffic attempting to exploit this vulnerability. It's essential for security teams to conduct inventory assessments of all Apache HTTP Server deployments within their infrastructures and confirm that they are not operating a vulnerable version. Furthermore, ongoing monitoring for unusual HTTP/2 traffic patterns can help in detecting potential exploitation attempts early on, minimizing the risk of successful attacks. Maintaining a security posture that includes regular updates and vulnerability assessments will reduce the likelihood of future incidents stemming from similar vulnerabilities.
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Apache Software Foundation Apache HTTP Server | >= 2.4.0 and <= 2.4.68Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- Apache HTTP Server 2.4.0 through 2.4.68 (mod_http2)
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? No. This is a use-after-free memory bug. Generic WAF rules do not recognise the input that triggers it; only a rule written for this specific CVE can, and only if the triggering request has a recognisable shape.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- CISA SSVC
- exploitation none, automatable yes, technical impact totalAssessed by CISA 1 Oct 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Timeline
- 1 Oct 2026Published
- 1 Oct 2026CISA SSVC assessment: exploitation nonesame day later
- 1 Oct 2026CVE record last updatedsame day later
- 2 Oct 2026Analysed by vulneraibility.com1 day later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2026-57941 being exploited?
Not confirmed. CVE-2026-57941 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.65% probability of exploitation in the next 30 days.
How severe is CVE-2026-57941?
CVE-2026-57941 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-57941?
Yes. A fix has been recorded for CVE-2026-57941. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-57941 affect?
CVE-2026-57941 affects Apache HTTP Server 2.4.0 through 2.4.68 (mod_http2). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-57941?
Upgrade to vendor-fixed Apache httpd release immediately; if not possible, disable HTTP/2 and apply WAF filters.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
2 references in the CVE record, grouped by the tags the record gives them.
Advisories (1)
- httpd.apache.org /security/vulnerabilities_24.html
Other links (1)
- openwall.com /lists/oss-security/2026/10/01/19
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.