ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. Prior to 3.0.16, the multipart/form-data request body parser in libmodsecurity silently removes embedded line breaks from non-file form-field values before exporting them to ARGS and ARGS_POST because src/request_body_processor/multipart.cc overwrites reserved bytes in m_reserve instead of appending the current buffer. This creates a parser differential between ModSecurity and backend applications that preserve line breaks in form fields, allowing rules that inspect ARGS or ARGS_POST to miss payloads whose dangerous syntax depends on a line break. This issue is fixed in version 3.0.16.
CVE-2026-52747
This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 62% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.6
- EG Score
- 8.6(medium)
- EPSS
- 38.3%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 14, 2026
Advisory Details (3)
Auto-updated Jul 10, 2026Multipart form-data parser silently strips embedded line breaks from form-field values, enabling request-body inspection bypass · Advisory · owasp-modsecurity/ModSecurity · GitHub
https://github.com/owasp-modsecurity/ModSecurity/security/advisories/GHSA-rcw9-2f5r-7p88v3.0.16
Patch available: owasp-modsecurity/ModSecurity v3.0.16
https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v3.0.16commit 875504c27581 (owasp-modsecurity/ModSecurity)
Fix landed in owasp-modsecurity/ModSecurity commit 875504c27581 — awaiting tagged release
https://github.com/owasp-modsecurity/ModSecurity/commit/875504c2758169c41be1ad2f0cc64d896b7815d7Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-10 21:53 UTCEG score recompute
- 2026-07-10 21:52 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-52747?
When was CVE-2026-52747 disclosed?
Is CVE-2026-52747 actively exploited?
What is the CVSS score of CVE-2026-52747?
How do I remediate CVE-2026-52747?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-52747
Is Your Infrastructure Affected by CVE-2026-52747?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.