Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-57941

httpd: Apache HTTP Server: mod_http2 use-after-free / wild write via shared session->bbtmp re-entrancy

Overview

Published
1 Oct 2026
Modified
5 Oct 2026
Critical CVE
1 Registry packages
40 OS packages
13 Linux distributions
Yes Fix available

Description

Use After Free vulnerability in Apache HTTP Server's mod_http2 via shared session->bbtmp re-entrancy

This issue affects Apache HTTP Server: from 2.4.0 through 2.4.68.

Source: OX vulnerability database

Severity

9.8 · CRITICAL

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-416

Affected packages · 1

Packages affected by CVE-2026-57941
EcosystemPackageVulnerableFixed in
Bitnami apache >=2.4.0, <2.4.69 2.4.69

Open a package to see all its vulnerabilities.

Operating systems · 37 fixes

Azure Linux 1 release · 1 package

fixed 1
httpd
Azure Linux fixes for CVE-2026-57941
ReleasePackageFixed in
3.0 httpd 0:2.4.69-1.azl3

Photon OS 2 releases · 1 package

fixed 2
httpd
Photon OS fixes for CVE-2026-57941
ReleasePackageFixed in
4.0 httpd +3 2.4.69-1.ph4
5.0 httpd +3 2.4.69-1.ph5

Red Hat 3 releases · 2 packages

affected 3 fixed 4
jbcs-httpd24-mod-http2 mod-http2
Red Hat fixes for CVE-2026-57941
ReleasePackageFixed inAdvisory
7 jbcs-httpd24-mod-http2 affected —
8 (httpd:2.4) mod-http2 affected —
9 jbcs-httpd24-mod-http2 affected —
9 mod-http2 0:2.0.26-2.el9_4.4 RHSA-2026:98968
9 mod-http2 0:2.0.26-4.el9_6.3 RHSA-2026:98954
9 mod-http2 0:2.0.26-6.el9_8.3 RHSA-2026:98982

1 more row

SUSE Linux Enterprise 5 releases · 1 package

fixed 5
apache2
SUSE Linux Enterprise fixes for CVE-2026-57941
ReleasePackageFixed inAdvisory
12.5 apache2 +13 2.4.66-35.84.1 SUSE-SU-2026:5099-1
15.4 apache2 +5 2.4.66-150400.6.60.1 SUSE-SU-2026:5076-1
15.5 apache2 +5 2.4.66-150400.6.60.1 SUSE-SU-2026:5076-1
15.6 apache2 +5 2.4.66-150600.5.58.1 SUSE-SU-2026:5075-1
15.7 apache2 +6 2.4.66-150700.4.26.1 SUSE-SU-2026:5077-1

alma 2 releases · 1 package

fixed 2
mod-http2
alma fixes for CVE-2026-57941
ReleasePackageFixed in
10 mod-http2 2.0.29-5.el10_3.1
9 mod-http2 2.0.26-7.el9_9.1

alpine 4 releases · 1 package

fixed 4
apache2
alpine fixes for CVE-2026-57941
ReleasePackageFixed in
3.22 apache2 2.4.69-r0
3.23 apache2 2.4.69-r0
3.24 apache2 2.4.69-r0
edge apache2 2.4.69-r0

amazon linux 1 release · 2 packages

fixed 2
mod-http2 httpd
amazon linux fixes for CVE-2026-57941
ReleasePackageFixed in
2023 mod-http2 +5 1:2.4.69-1.amzn2023.0.2
2023 httpd +15 2.4.69-1.amzn2023.0.2

debian 4 releases · 1 package

affected 1 fixed 3
apache2
debian fixes for CVE-2026-57941
ReleasePackageFixed in
11 apache2 affected
12 apache2 2.4.71-1~deb12u1
13 apache2 2.4.69-1~deb13u1
14 apache2 2.4.69-1

echo 1 release · 1 package

fixed 1
apache2
echo fixes for CVE-2026-57941
ReleasePackageFixed in
apache2 2.4.68-1~deb13u1+e2

minimos 1 release · 1 package

fixed 1
apache2
minimos fixes for CVE-2026-57941
ReleasePackageFixed in
apache2 2.4.69-r0

openSUSE 1 release · 1 package

fixed 1
apache2
openSUSE fixes for CVE-2026-57941
ReleasePackageFixed inAdvisory
Tumbleweed apache2 2.4.71-1.1 openSUSE-SU-2026:12537-1

rocky 2 releases · 1 package

fixed 2
mod-http2
rocky fixes for CVE-2026-57941
ReleasePackageFixed in
10 mod-http2 2.0.29-5.el10_3.1
9 mod-http2 2.0.26-7.el9_9.1

ubuntu 5 releases · 1 package

fixed 5
apache2
ubuntu fixes for CVE-2026-57941
ReleasePackageFixed in
18.04-ESM apache2 2.4.29-1ubuntu4.27+esm12
20.04-ESM apache2 2.4.41-4ubuntu3.23+esm8
22.04 apache2 2.4.52-1ubuntu4.24
24.04 apache2 2.4.58-1ubuntu8.16
26.04 apache2 2.4.66-2ubuntu2.5

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.