Read the docs

HTML entity decoding gaps in ModSecurity let attackers bypass rules

Priority LOW 28CWE-172Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

ModSecurity versions before 2.9.15 and from 3.0.0 before 3.0.17 are affected. The t:htmlEntityDecode transformation recognizes only a small subset of named HTML entities, so rules that depend on it can inspect different bytes than a browser or backend (CWE-172). A remote attacker can encode ASCII separators and operators with unhandled entity names, including aliases, to bypass such rules. The v3 decoder also accepts prefix matches instead of requiring an exact entity-token length, which can turn invalid longer names into different bytes.

Written with Claude Haiku 5.5 from the sources below · 2026-11-09

Description from the CNA

ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. Prior to 2.9.15 and 3.0.17, t:htmlEntityDecode recognizes only a small subset of named HTML entities, so rules that depend on the transformation can inspect different bytes than a browser or backend. Attackers can encode ASCII separators and operators with unhandled entity names, including aliases, to bypass rules that depend on the transformation. The v3 decoder also accepts prefix matches instead of requiring an exact entity-token length, which can transform invalid longer names into different bytes. This issue is fixed in versions 2.9.15 and 3.0.17.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00316 24th percentileScored 2026-11-16
Fix Fixed ModSecurity (owasp-modsecurity): 2.9.15, 3.0.17

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
owasp-modsecurityModSecuritybefore 2.9.15; 3.0.0 to before 3.0.172.9.15, 3.0.17Patch availableCNA
  • ModSecurity Vendorowasp-modsecurity Affected before 2.9.15; 3.0.0 to before 3.0.17 Fixed in 2.9.15, 3.0.17 Patch available CNA

Remediation

Upgrade ModSecurity 2.x to 2.9.15 and ModSecurity 3.x to 3.0.17.

Written with Claude Haiku 5.5 from the sources below · 2026-11-09

  • Fix · CNA ModSecurity (owasp-modsecurity) Fixed in 2.9.15, 3.0.17

Timeline

  1. 2026-11-09 Threatist record created from CVE-2026-61812
  2. 2026-11-11 Priority changed: MEDIUM → LOW
  3. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2026-85491 ModSecurity filename* parsing lets uploads bypass multipart rules CVSS 3.1HIGH 8.6
  • TI-2026-85489 ModSecurity skips response body inspection for mixed-case types CVSS 3.1HIGH 8.6
  • TI-2026-37865 ModSecurity: Multipart form-data parser silently strips embedded line breaks from… CVSS 3.1HIGH 8.6
  • TI-2025-40548 FACTION Unauthenticated Custom Extension Upload leads to RCE CVSS 3.1CRITICAL 9.8
  • TI-2022-07517 Path Traversal in ESAPI CVSS 3.1CRITICAL 9.8
  • TI-2026-30581 ModSecurity: Unsigned integer underflow in @verifySSN / @verifyCPF / @verifySVNR operators CVSS 4.0HIGH 8.2
See all 59 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences