CVE-2026-73856: 
ModSecurity vulnerability analysis and mitigation

Overview

CVE-2026-73856 is a response body inspection bypass vulnerability in ModSecurity, an open-source cross-platform WAF engine for Apache, IIS, and Nginx. Affecting versions 3.0.0 through 3.0.16, the flaw allows unauthenticated network attackers to bypass phase 4 RESPONSE_BODY rules by triggering a case-sensitive Content-Type comparison mismatch. The vulnerability was disclosed on September 30, 2026, and fixed in version 3.0.17. It carries a CVSS v3.1 base score of 8.6 (High) (GitHub Advisory, Red Hat Bugzilla).

Technical details

The root cause is improper handling of case sensitivity (CWE-178, CWE-200) in src/transaction.cc. ModSecurity's processResponseBody() and appendResponseBody() functions perform a case-sensitive std::set::find() lookup of the response Content-Type value against the SecResponseBodyMimeType configuration entries (which are stored in lowercase by default). When a backend returns a semantically equivalent but mixed-case Content-Type header — such as Text/Html instead of text/html — the lookup fails, and ModSecurity skips all RESPONSE_BODY inspection for that response, forwarding the unfiltered body to the client. The fix in commit 23ccd92 applies utils::string::tolower() to the Content-Type value before the set lookup, ensuring case-insensitive matching. A public Python PoC is available in the GitHub Security Advisory demonstrating the bypass (GitHub Advisory, Fix Commit).

Impact

Successful exploitation allows an unauthenticated remote attacker to receive response bodies that phase 4 RESPONSE_BODY rules would otherwise block, including sensitive error messages, stack traces, debug output, credentials, and secret keys. The scope is marked as Changed in CVSS because the bypass affects the WAF's protective boundary, potentially exposing data from backend applications beyond ModSecurity's own security scope. There is no integrity or availability impact, but the confidentiality impact is rated High, as complete sensitive response content can be leaked to unauthorized actors (GitHub Advisory, Red Hat Bugzilla).

Exploitability

A public proof-of-concept Python script is available in the GitHub Security Advisory, demonstrating the bypass in a local nginx + ModSecurity lab environment. The exploit requires no authentication, no user interaction, and low attack complexity — it is fully automatable via a crafted HTTP request. The EPSS score is approximately 0.565%, and there is no current evidence of in-the-wild exploitation or CISA KEV catalog listing. No specific threat actor attribution has been reported (GitHub Advisory, Feedly).

Exploitation steps

  1. Reconnaissance: Identify targets running ModSecurity 3.0.0–3.0.16 with SecResponseBodyAccess On and SecResponseBodyMimeType configured (e.g., text/html, text/plain). These are commonly deployed with nginx using ngx_http_modsecurity_module.
  2. Identify a reflective Content-Type endpoint: Find a backend endpoint that reflects an attacker-controlled parameter into the Content-Type response header (e.g., a ?format= query parameter that sets the response content type).
  3. Craft a mixed-case Content-Type request: Send an HTTP GET request with a query parameter that causes the backend to return a mixed-case Content-Type value, such as Text/Html instead of text/html:
    curl -s 'http://target/config?format=Text/Html'
  4. Trigger the bypass: ModSecurity's case-sensitive std::set::find() lookup fails to match Text/Html against the configured text/html entry, so RESPONSE_BODY inspection is skipped entirely.
  5. Receive unfiltered response: The backend's full response body — including sensitive data such as SECRET_KEY, DB_PASSWORD, stack traces, or debug output — is returned to the attacker with HTTP 200, bypassing any phase 4 deny rules (GitHub Advisory).

Indicators of compromise

  • Network: HTTP requests to application endpoints with unusual mixed-case Content-Type values in responses (e.g., Text/Html, Text/Plain); unexpected HTTP 200 responses from endpoints that should return 403/500 under WAF rules.
  • Logs: ModSecurity audit/debug logs containing entries such as Response Content-Type is Text/Html. It is not marked to be inspected. at debug level 5, indicating body inspection was skipped; absence of expected phase 4 rule trigger logs for sensitive response content.
  • Application Logs: Backend access logs showing repeated requests to endpoints with query parameters controlling Content-Type output (e.g., ?format=Text/Html), particularly from external IPs.
  • WAF Logs: Nginx error logs showing ModSecurity loaded but no id:30001 (or equivalent RESPONSE_BODY rule) denial entries despite sensitive content being served (GitHub Advisory).

Mitigation and workarounds

Upgrade ModSecurity to version 3.0.17 or later, which resolves the issue by applying case normalization (tolower()) to the Content-Type value before comparison in src/transaction.cc (ModSecurity v3.0.17 Release, Fix Commit). As a temporary workaround for systems that cannot immediately upgrade, implement network-level controls to restrict access to ModSecurity-protected applications, and audit backend applications to prevent reflection of attacker-controlled values into Content-Type response headers. Additionally, review SecResponseBodyMimeType configurations and consider adding mixed-case variants as a short-term measure, though upgrading remains the definitive fix (Red Hat Bugzilla).

Community reactions

The vulnerability was reported by researcher zuesdevil and credited in the ModSecurity v3.0.17 release notes. Red Hat has tracked the issue under Bugzilla bug 2567811 with High severity. The Hacker News weekly recap for the relevant period referenced the ModSecurity September 2026 batch of fixes, and community blog posts on dev.to discussed the legacy branch implications of the fix. No major vendor statements beyond the GitHub Security Advisory and Red Hat tracking have been identified (GitHub Advisory, Red Hat Bugzilla).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Affected

bookworm

modsecurity

Affected

sid

modsecurity

Affected

trixie

modsecurity

Affected

Ubuntu

Unknown

devel

modsecurity

Unknown

focal (esm-apps)

modsecurity

Unknown

jammy

modsecurity

Unknown

jammy (esm-apps)

modsecurity

Unknown

noble

modsecurity

Unknown

noble (esm-apps)

modsecurity

Unknown

resolute

modsecurity

Unknown

resolute (esm-apps)

modsecurity

Unknown

Source: This report was generated using AI

Related ModSecurity vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-73856HIGH8.6
  • ModSecurity logoModSecurity
  • modsecurity
NoYesNov 05, 2026
CVE-2026-73857HIGH7.5
  • ModSecurity logoModSecurity
  • modsecurity
NoYesNov 09, 2026
CVE-2026-61812MEDIUM6.3
  • ModSecurity logoModSecurity
  • cpe:2.3:a:owasp:modsecurity
NoYesNov 09, 2026
CVE-2026-104259MEDIUM5.4
  • ModSecurity logoModSecurity
  • modsecurity
NoYesNov 09, 2026
CVE-2026-61813LOW3.7
  • ModSecurity logoModSecurity
  • modsecurity
NoYesNov 05, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management