Skip to content
major vulnerability· requires attention

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.

Applications

CVE-2026-57941

9.8
Critical
EPSS 0.44%Patch availableOct 2, 2026

Use-after-free in Apache mod_http2 enabling RCE or DoS

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.44% 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.

executive summary
technical analysis
affected
Apache HTTP Server 2.4.0 through 2.4.68 (mod_http2)
impact

Remote code execution or server crash via crafted HTTP/2 requests exploiting a use-after-free in mod_http2.

action required

Immediate action required

affected versions
Apache Software Foundation Apache HTTP Server
  • affected>= 2.4.0 and <= 2.4.68

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free