Skip to content
NewA calmer, faster ZeroHour

CVE-2026-73856

Case-sensitive Content-Type skips ModSecurity response-body inspection

CVSS 3.1
8.6 high
EPSS
—
Published
·
Modified
Analyze CVE-2026-73856 with Vani AIImpact, affected versions, exploitation status, mitigations and detection

From 3.0.0 until 3.0.17, ModSecurity compares a response Content-Type with SecResponseBodyMimeType entries case-sensitively. A mixed-case media type equivalent to a configured lowercase type is treated as unconfigured, so RESPONSE_BODY inspection is skipped. An unauthenticated network requester can then receive content a phase 4 rule would block, including sensitive error or debug data. Apache, IIS, and Nginx deployments in that range are affected.

What to do: Upgrade ModSecurity to 3.0.17.

ProductAffectedFixed in
ModSecurity3.0.0 until 3.0.173.0.17
Estimated exposure
No basis for an estimate.

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description · NVD

ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. From 3.0.0 until 3.0.17, src/transaction.cc compares a response Content-Type value against SecResponseBodyMimeType entries case-sensitively. A mixed-case response media type that is semantically equivalent to a configured lowercase type can therefore be treated as unconfigured, causing ModSecurity to skip RESPONSE_BODY inspection. An unauthenticated requester can then receive response content that a phase 4 rule would otherwise block, including sensitive error or debug data. This issue is fixed in version 3.0.17.

Weakness
CWE-178
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

In the news

0 stories

No ingested article mentions this CVE yet.