ModSecurity: PCRE2 `@rxGlobal` match-limit errors are converted to no-match
- Exploited
- No known exploitation
- Fix
- Fixed in 3.0.17
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.0.17.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 23/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
ModSecurity, an open source web application firewall engine used with Apache, IIS, and Nginx, can be made to let requests through that should be blocked. This is reached remotely, without logging in, when attacker-controlled input exhausts the PCRE2 match limit in an @rxGlobal rule that has a compensating rule, and only affects PCRE2 deployments with that setup.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.8/10CVSS 5.8
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.0.17.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- owasp-modsecurity ModSecurity
From 3.0.5 · fixed in 3.0.17
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-103932
Is CVE-2026-103932 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-103932?
ModSecurity: from 3.0.5 before 3.0.17.Source: cve.now feed data
How do I fix CVE-2026-103932?
Upgrade to a fixed version: 3.0.17.Source: cve.now feed data