Read the docs
TI-2026-85486 Aliases CVE-2026-103932

ModSecurity PCRE2 @rxGlobal turns match-limit errors into no-match

Priority LOW 26CWE-253Published · Updated

Key facts

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

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

Summary

ModSecurity from 3.0.5 before 3.0.17 is affected. In the PCRE2 implementation of @rxGlobal, a match-limit error is converted into an ordinary no-match result. When attacker-controlled input exhausts SecPcreMatchLimit, rules that check MSC_PCRE_LIMITS_EXCEEDED do not run, so a request that should be rejected can pass the WAF. The issue needs a limit-exhaustible expression and a compensating rule, so it is not a universal bypass (CWE-253).

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

Description from the CNA

ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. From 3.0.5 until 3.0.17, the PCRE2 implementation of @rxGlobal in src/utils/regex.cc converts pcre2_match match-limit errors into an ordinary no-match result instead of propagating a non-OK RegexResult. When attacker-controlled input exhausts SecPcreMatchLimit, rules that rely on MSC_PCRE_LIMITS_EXCEEDED or its TX compatibility indicator do not run, so a request that should be rejected can pass through the WAF. The issue affects PCRE2 deployments that use @rxGlobal with a limit-exhaustible expression and a compensating rule; it is not a universal WAF bypass. This issue is fixed in version 3.0.17.

Why it matters now

EPSS 0.00321 25th percentileScored 2026-11-07
Fix Fixed ModSecurity (owasp-modsecurity): 3.0.17

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
owasp-modsecurityModSecurity3.0.5 to before 3.0.173.0.17Patch availableCNA
  • ModSecurity Vendorowasp-modsecurity Affected 3.0.5 to before 3.0.17 Fixed in 3.0.17 Patch available CNA

Remediation

Upgrade ModSecurity to version 3.0.17, the fixed version.

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

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

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-11-05 Threatist record created from CVE-2026-103932
  2. 2026-11-06 Affected versions changed · Red Hat
  3. 2026-11-06 CVSS score added · Red Hat
  4. 2026-11-07 Priority changed: MEDIUM → LOW

References

Other 3

  • 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
  • TI-2026-23748 libModSecurity3 denial of service via segfault when using t:hexDecode on single-character query strings CVSS 4.0HIGH 8.2
  • TI-2025-19980 Libmodsecurity3 has possible bypass of encoded HTML entities CVSS 4.0HIGH 7.9
See all 56 →

Sources

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