Monday 16 November
Global

Your region, kept on this device.

ModSecurity WAF Flaws Allow Upload Filter Bypass and Possible Code Execution

Severity
High
Highest CVSS
8.6
Exploited
Not known
Sources
1

CVE-2026-104269 (GHSA-5pww-8rfg-9crf): 3.0.0 and later multipart parser ignores RFC 2231 filename and lets a request with filename="safe.jpg" plus filename=UTF-8''shell.php pass CRS checks, while Go, Python (Flask, FastAPI), Node.js and Java Spring backends may save shell.php. No patch is listed. CVE-2026-73857 (GHSA-jx3r-phvx-2jmj, CWE-787/CWE-824): uninitialised pointer use allowing a fixed write to an attacker-chosen address, affecting 3.0.15, 3.0.16 and v3 master only when SecParseXmlIntoArgs is On or OnlyArgs (default Off). Advisory lists 3.0.17 as fixed but text says a fix is not yet available; verify the release before upgrading. Set SecParseXmlIntoArgs Off now and do not rely on the WAF for upload validation.

For security analysts · Written by AI from 1 source · Wrong?

What to do

  1. Check that SecParseXmlIntoArgs is set to Off, the workaround given in the advisory for CVE-2026-73857.
  2. Upgrade ModSecurity once you have confirmed on the official project page that the fixed release is available.
  3. Do not rely on the WAF alone to judge uploads; have applications ignore the client-supplied filename and generate their own safe name.
  4. Block script extensions such as .php and store uploads outside the web root, as general good practice not stated in the advisory.

Written by AI from the sources, checked against them

Vulnerabilities

Full story timeline · 3 updates

  1. Thu 5 NovemberCVE-2026-104269 published, CVSS 8.6NVD
  2. Mon 9 NovemberModSecurity Patches Two High-Severity Flaws Allowing WAF Bypass and Potential Remote Code ExecutionCyber Security News
  3. CVE-2026-73857 published, CVSS 7.5NVD

Who reported · 1 outlet

Cyber Security News

Who and what is in it

Products

Report a problem