
YARA rules to inventory Apache mod_http2 presence, HTTP/2 config directives and source markers for CVE-2026-119618 exposure triage, with a fixed-build hash allowlist.
YARA: Search for vulnerable
Rule file: CVE-2026-119618-mod_http2-detection-v4.4.yar
Date: 2026-11-14
An inventory and exposure aid for CVE-2026-119618, the race condition in
assign_headers() of Apache mod_http2 that can lead to remote code execution.
The rules find where mod_http2 exists on disk and where configuration files
refer to HTTP/2. They leave out binaries you have verified as patched.
mod_http2.so carry
the same markers. A match means "the module is here", nothing more.h2/h2c.| Component | Affected | Fixed |
|---|---|---|
| Apache HTTP Server | 2.4.55 – 2.4.70 | 2.4.71 (commit 824beab) |
| Standalone mod_h2 | 2.0.8 – 2.0.42 | sources disagree on whether a fixed release exists |
Distributions backport the fix without changing the upstream version number.
Example: the fixed RHEL 9 package is mod_http2-2.0.26-7.el9_9.1, which is
still "2.0.26". Never conclude "vulnerable" from a version string alone.
Every rule has a tag, so output can be filtered with yara -t <tag>.
| Tag | Rule (prefix CVE_2026_119618_) | Classification | Meaning of a match |
|---|---|---|---|
module | mod_http2_ELF | MODULE_PRESENT | Linux/Unix shared module or static httpd containing mod_http2 |
module | mod_http2_PE | MODULE_PRESENT | Windows build containing mod_http2 (file may be named .so) |
module | mod_http2_MachO | MODULE_PRESENT | macOS build containing mod_http2 |
module | mod_http2_Generic_Binary_Candidate | MODULE_CANDIDATE | mod_http2 markers in other binary data: archives, image layers, core dumps, object files |
proxy | mod_proxy_http2_Binary | PROXY_MODULE_PRESENT | mod_proxy_http2; inventory only, not a finding for this CVE |
config | mod_http2_LoadModule_Config | CONFIG_LOAD_DIRECTIVE | Non-comment LoadModule http2_module line |
config | HTTP2_Protocols_h2_Config | CONFIG_H2_TLS | Protocols line listing h2 (HTTP/2 over TLS) |
config | HTTP2_Protocols_h2c_Config | CONFIG_H2C | Protocols line listing h2c (cleartext HTTP/2) |
config | HTTP2_Additional_Directives_Config | CONFIG_H2_DIRECTIVE | Other H2… directive; not proof that HTTP/2 is on |
source | mod_http2_Source | SOURCE_PRESENT | mod_http2.c in a source or build tree |
source | mod_http2_Source_Version | SOURCE_VERSION | h2_version.h; yara -s prints the version literal |
source | mod_http2_Source_Affected_Function | SOURCE_AFFECTED_FUNCTION | Source file containing assign_headers(; review it against commit 824beab |
version | mod_http2_Embedded_Version_Hint | BINARY_VERSION_HINT | mod_h2/x.y.z string; unverified marker, see limitations |
Three private helper rules do not appear in the output:
known_fixed_build – hash allowlist of verified fixed mod_http2 binaries.known_fixed_proxy_build – the same for mod_proxy_http2.looks_like_documentation – keeps the config rules quiet on Markdown and
ChangeLog files such as /usr/share/doc/mod_http2/README.md.The four module rules and the proxy rule do not report a file whose hash is
on the allowlist. A binary that is not listed is always reported: unknown
never means patched.
Current entries:
| File | Hash | Package |
|---|---|---|
mod_http2.so | SHA-1 47474b88dd405706962bd7b433e7f1a34052da61 | assumed RHEL 9 x86_64 mod_http2-2.0.26-7.el9_9.1, to be confirmed |
mod_http2.so | SHA-256 7b0df6ec28d6e7795844bf391c6648f5c67dcedc2a8a93311c7eff4190fc703e | not recorded yet |
mod_http2.so | SHA-256 40bb1ad543422255514c2427e5864211f0d1a60ed02f7397daad8bc21389cd89 | not recorded yet |
mod_proxy_http2.so | SHA-256 bb5b961e6979e3aff80312dbbf99c1055e4349ce133849bff07ee40c2b350718 | not recorded yet |
rpm -q --changelog mod_http2 | grep CVE-2026-119618).sha256sum /usr/lib64/httpd/modules/mod_http2.so
rpm -qf /usr/lib64/httpd/modules/mod_http2.so
CVE_2026_119618_known_fixed_build, joined with or, and
note distribution, package and architecture in the comment above it:
// RHEL 9 x86_64 mod_http2-2.0.26-7.el9_9.1
hash.sha256(0, filesize) == "<lower-case sha256>" or
Each architecture and each package release has its own hash.
Config, source and version matches are not suppressed on patched hosts. YARA evaluates each file on its own and cannot know that a config file belongs to a host with a patched module. Use the tag filter below instead.
# Syntax check
yarac CVE-2026-119618-mod_http2-detection-v4.4.yar /dev/null
# Triage view: only module binaries that are NOT on the fixed-build allowlist.
# Empty output on a host whose builds are all allowlisted.
yara -t module -r CVE-2026-119618-mod_http2-detection-v4.4.yar /
# Full inventory with matched strings and offsets
yara -r -s CVE-2026-119618-mod_http2-detection-v4.4.yar /usr/lib64/httpd /etc/httpd /opt
# Configuration references only
yara -t config -r CVE-2026-119618-mod_http2-detection-v4.4.yar /etc/httpd
Requirements: YARA 4.x built with the hash module (standard in distribution
packages). No external variables.
A host is exposed only if all of these hold:
mod_http2 is present and the build is not fixed
(module match that is not allowlisted, then check the package).apachectl -M | grep http2, or httpd -l for static
builds, or grep mod_http2 /proc/<pid>/maps for the running process.Protocols line with h2 or h2c. Without
one, httpd serves only HTTP/1.1.
Check from outside with openssl s_client -connect host:443 -alpn h2.After installing a fixed package, restart httpd. Until then the running process still has the old module in memory, even though the file on disk is patched.
<IfModule>,
<IfDefine>, includes, inactive virtual hosts, backups or .rpmnew files.BINARY_VERSION_HINT is unverified. It is not confirmed that compiled
modules embed a mod_h2/x.y.z string. Check with
strings mod_http2.so | grep -E 'mod_h2|2\.0\.[0-9]+'; remove the rule if not.SOURCE_AFFECTED_FUNCTION is untested against a real source tree, and
patched source contains the function too.The rule file was written without access to a YARA engine. Field use so far
showed that the file compiles and that the allowlist removes the mod_http2_ELF
match on a patched RHEL 9 host (observed with v4.2/v4.3). Not yet confirmed on
real files: the proxy allowlist, the documentation filter, the tag filter, and
the PE and Mach-O rules.