ModSecurity Flaws Enable Malicious Uploads, Crashes
Two high-severity vulnerabilities in the open-source web application firewall could allow remote code execution, according to maintainer advisories published September 30.
Updated on Nov. 9, 2026 in Cybersecurity

ModSecurity maintainers disclosed two high-severity flaws in the open-source web application firewall on September 30. The flaws allow malicious file uploads and server crashes that could lead to remote code execution.
Why it matters
ModSecurity is used alongside Apache, IIS, and Nginx to protect web applications, so a flaw in the firewall itself can weaken defenses for the sites it guards. The filename mismatch shows how differences in parsing between a firewall and the application behind it can open a path for attackers.
Maintainer advisories list CVE-2026-104269 as affecting ModSecurity 3.0.0 and later, and the XML flaw affecting versions 3.0.15 and 3.0.16 carries an estimated CVSS score near 7.5. Whether attackers have exploited either flaw in practice is not stated.
The players
ModSecurity
ModSecurity is an open-source web application firewall widely used with Apache, IIS, and Nginx to inspect and filter web traffic.
Tobias Klein
Tobias Klein is a security researcher credited with reporting the XML parsing flaw tracked as CVE-2026-73857.
The details
Researchers 0xkalawy and ZeyadZonkorany found that an attacker can send filename="safe.jpg" together with filename*=UTF-8''shell.php in one request, because ModSecurity's multipart parser does not support RFC 2231 while PHP's native upload handling is not affected. Researcher Tobias Klein reported CVE-2026-73857, which can cause a single crafted request to make a worker process use an uninitialized pointer; that path is reachable only when SecParseXmlIntoArgs is On or OnlyArgs, and it is Off by default.
Timeline
September 30: Maintainer airween published two GitHub advisories.
November 9: An article about the ModSecurity flaws was published.
Big Picture
The filename flaw comes from ModSecurity's multipart parser not supporting RFC 2231, while PHP's native upload handling does not share the weakness. This kind of parser disagreement between a web application firewall and the application it protects is what allows the bypass.
Sites running ModSecurity 3.0.15 or 3.0.16 with the XML parsing path enabled are the ones most directly affected, and the advisory points to 3.0.17 as the patched release. Administrators who rely on the firewall to filter uploads should verify their version and their SecParseXmlIntoArgs setting.
The takeaway
Check which ModSecurity version is running and whether SecParseXmlIntoArgs is enabled, since both determine exposure to the XML flaw. Keeping web application firewalls patched matters as much as the applications they protect.
Further reading
For related coverage, browse the Cybersecurity section.







