CVE-2026-44631 is a buffer underwrite / heap underflow vulnerability in Apache HTTP Server affecting versions 2.4.0 through 2.4.67. The flaw occurs in ap_regname when processing crafted regular expressions used in server configuration, including .htaccess contexts. Available details indicate the bug is caused by a signed char overflow that can drive an out-of-bounds write before the start of a heap buffer during regex name handling. Apache fixed the issue in version 2.4.68.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
.htaccess or other configuration inputs that can introduce such regex patterns. These measures are only temporary risk reductions and do not replace upgrading.Patch, then assume compromise.
.htaccess, are updated.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
22 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An Apache vulnerability cited as an example of shared attribution across multiple AI-assisted discovery paths; no technical details are provided.
A vulnerability affecting IBM HTTP Server configurations that use regular expressions with more than 128 captures, including in .htaccess files.
A heap underwrite vulnerability in Apache HTTP Server ap_regname caused by signed char overflow in crafted regex configurations.
A char overflow / heap underwrite vulnerability in Apache HTTP Server triggered during parsing of custom regular expressions.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.