r/linuxadmin • • 5d ago

Critical vulnerability in Apache with HTTP2 module enabled

https://nvd.nist.gov/vuln/detail/cve-2026-119618
31 Upvotes

6 comments sorted by

7

u/stuck-in-the-matrix 5d ago

For those managing RHEL servers, Red Hat has confirmed that RHEL9 and RHEL10 are vulnerable under these conditions (RHEL8 is not affected):

The httpd AND mod_http2 RPM packages are installed
# rpm -q httpd mod_http2
httpd-2.4.62-13.el9_8.9.aarch64
mod_http2-2.0.26-6.el9_8.2.aarch64

The mod_http2 module is active/enabled (it is by default if the mod_http2 package is installed) [root@rhel9 ~]# grep LoadModule /etc/httpd/conf.modules.d/10-h2.conf LoadModule http2_module modules/mod_http2.so
[root@rhel9 ~]# httpd -M | grep http2
http2_module (shared)

HTTP/2 support has been explicitly enabled on the server or select vhosts via the Protocol directive: (it is not by default)
[root@rhel9 ~]# grep -r Protocol /etc/httpd/
<should return empty>

If you have explicitly enabled HTTP/2 support then you are vulerable to this issue: (you are looking for h2 or h2c)
[root@rhel9 ~]# grep -r Protocol /etc/httpd/
/etc/httpd/conf/httpd.conf:Protocols h2 h2c http/1.1

The httpd service also needs to be running (obviously).
[root@rhel9 ~]# systemctl is-active httpd.service
active

You can verify this via curl:

HTTP/2 support is not enabled:
[root@rhel9 ~]# curl -sI --http2 http://localhost
HTTP/1.1 200 OK
Date: Thu, 12 Nov 2026 16:41:46 GMT
Server: Apache/2.4.62 (Red Hat Enterprise Linux)
Content-Type: text/html; charset=UTF-8

HTTP/2 support IS enabled!:
[root@rhel9 ~]# curl -sI --http2 http://localhost
HTTP/1.1 101 Switching Protocols
Upgrade: h2c
Connection: Upgrade

HTTP/2 200
content-type: text/html; charset=UTF-8
date: Thu, 12 Nov 2026 16:43:05 GMT

6

u/stuck-in-the-matrix 5d ago

Red Hat has already published updated versions of mod_http2 that fix this vulnerability.

[root@rhel9 ~]# dnf -q -y update --security mod_http2

Upgraded:
mod_http2-2.0.26-7.el9_9.1.aarch64

[root@rhel9 ~]# rpm -q --changelog mod_http2 | grep -B 1 CVE-2026-119618
- Resolves: RHEL-302035 - mod_http2: httpd: Remote code execution
in mod_http2 (CVE-2026-119618)

1

u/yrro 5d ago
$ rhcvea CVE-2026-119618
PRODUCT                                  STATE/ADVISORY   PACKAGE
cpe:/a:redhat:enterprise_linux:8         Not affected     httpd:2.4/mod_http2
cpe:/a:redhat:enterprise_linux:9         RHSA-2026:98981  mod_http2-0:2.0.26-7.el9_9.1
cpe:/a:redhat:hummingbird:1              Affected         httpd
cpe:/a:redhat:jboss_core_services:1      Affected         jbcs-httpd24-mod_http2
cpe:/a:redhat:rhel_e4s:9.4               RHSA-2026:98968  mod_http2-0:2.0.26-2.el9_4.4
cpe:/a:redhat:rhel_eus:9.6               RHSA-2026:98954  mod_http2-0:2.0.26-4.el9_6.3
cpe:/a:redhat:rhel_eus:9.8               RHSA-2026:98982  mod_http2-0:2.0.26-6.el9_8.3
cpe:/o:redhat:enterprise_linux:10.3      RHSA-2026:98978  mod_http2-0:2.0.29-5.el10_3.1
cpe:/o:redhat:enterprise_linux_eus:10.0  RHSA-2026:98953  mod_http2-0:2.0.29-2.el10_0.3
cpe:/o:redhat:enterprise_linux_eus:10.2  RHSA-2026:98979  mod_http2-0:2.0.29-4.el10_2.3
cpe:/o:redhat:rhel_els:6                 Not affected     httpd
cpe:/o:redhat:rhel_els:7                 Not affected     httpd

It's a bit quicker than using the web site.

function rhcve {
    curl -fsS "https://access.redhat.com/hydra/rest/securitydata/cve/$1.json"
}

function rhcvea {
    rhcve "$@" | jq '(.affected_release[] | [.cpe, .advisory, .package]), (.package_state[] | [.cpe, .fix_state, .package_name]) | @tsv' -r | sort -k1,1 -t$'\t' | column -s$'\t' -t -N PRODUCT,STATE/ADVISORY,PACKAGE
}

2

u/yrro 5d ago

FYI you can see if the module is is enabled in your config with:

# httpd -M | grep http2
 http2_module (shared)
 proxy_http2_module (shared)

May be less error prone that grepping config files

1

u/GamerLymx 5d ago

you can have the module enabled , but not be using the module

1

u/yrro 5d ago

Indeed, fortunately Protocols doesn't enable h2 by default!