Apache Tomcat HTTP/2 Request Headers Not Validated
CVE-2026-41293 is a low-severity improper input validation vulnerability in Apache Tomcat. Tomcat did not validate HTTP/2 request headers before exposing header values to applications through the Servlet API. As a result, an application that reasonably assumes Servlet API header values are specification-compliant could receive malformed or otherwise invalid header data, potentially triggering unexpected application behavior. Reported affected versions include Tomcat 11.0.0-M1 through 11.0.21, 10.1.0-M1 through 10.1.54, 9.0.0.M1 through 9.0.117, and 10.0.0-M1 through 10.0.27; some sources also indicate 8.5.0 through 8.5.100 may be affected, and older unsupported versions may also be impacted.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical-severity vulnerability in Apache Tomcat affecting third-party dependencies used in Atlassian products.
A low-severity Apache Tomcat vulnerability where HTTP/2 request headers were not properly validated, potentially causing unexpected application behavior when applications assumed Servlet API header values were specification compliant.
The version that knows your environment.
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.