Servers and applications
CVE-2026-103932
PCRE2 `@rxGlobal` match-limit errors are converted to no-match
- Severity
- Medium 5.8
- Published
- 30 Sept 2026
- Last changed
- 9 Nov 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 3.0.17
- Exploit chance
- 0.3% in the next 30 daysHigher than 25% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- CWE-253
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Change some data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N- Also known as
- GHSA-5m93-4h75-3p2w
- Sources
- CVE Program, Project advisories (GitHub)
Description
In ModSecurity v3.0.16, the PCRE2 implementation of @rxGlobal converts match-limit errors into ordinary no-match/success. An unauthenticated remote client can therefore cause a request to pass a compensating rule in an affected ruleset by supplying input that exhausts SecPcreMatchLimit.
The suggested severity is Moderate. This is a conditional security-control fail-open: it affects PCRE2 deployments whose rules use @rxGlobal and rely on ModSecurity's documented PCRE-limit indicator. It is not a universal WAF bypass.
gpt5.6-sol cross-checked by Opus 4.8 + K3. Fable 5 could not cross-check due to safeties being triggered.
The issue was reproduced at commit 7ea9fefbe0ba409d8733b4d682c8c4c059cd028d (v3.0.16).
In src/utils/regex.cc, lines 244–343, the PCRE2 branch of modsecurity::Utils::Regex::searchGlobal calls pcre2_match at lines 262–263. Unlike the PCRE1 branch at lines 288–291, it does not convert the engine return through to_regex_result or propagate a non-OK result.
Affected software
| Software | Affected versions |
|---|---|
ModSecurityServers and applications · cna:owasp-modsecurity|modsecurity |
|
ModSecurityServers and applications · github:owasp-modsecurity/modsecurity |
|
About ModSecurity
web application firewall (WAF) module
- Docker Hub pulls
- 7,086,565Docker Hub, 15 Nov 2026
- GitHub stars
- 9,872GitHub, 15 Nov 2026
- Forks
- 1,761GitHub, 15 Nov 2026
- Latest release
- v3.0.17GitHub, 15 Nov 2026
- Released
- 29 Sept 2026GitHub
- Developer
- Trustwave HoldingsWikidata
- License
- Apache Software License 2.0Wikidata
- Written in
- CWikidata
- First published on GitHub
- 2 Feb 2011GitHub
Website Source code Docker image
Vulnerabilities in ModSecurity
- In our list
- 36
- Published in the last 12 months
- 12
- Critical, last 12 months
- 0
- High, last 12 months
- 6
- Known exploited
- 0
- CVE-2026-61813ModSecurity: Incorrect libcurl TLS hostname verification setting in HttpsClient::downloadLow 3.7 5 Nov 2026
- CVE-2026-104269RFC 2231 `filename*` Parameter Bypasses Multipart Filename Rules on RFC-Compliant Backends (Go, Python, Node, Java)High 8.6 30 Sept 2026
- GHSA-4j47-8qcr-jf59`t:base64DecodeExt` silently discards the entire decoded value on a malformed base64 padding group, bypassing rule matchingMedium 5.8 30 Sept 2026
- CVE-2026-104259removeComments Transformation Fails to Strip Adjacent Comments, Enabling WAF Rule BypassMedium 5.4 30 Sept 2026
- CVE-2026-73857ModSecurity v3 XML Request Body Processor Uninitialized Pointer Dereference VulnerabilityHigh 7.5 30 Sept 2026
- CVE-2026-73856Response Body Inspection BypassHigh 8.6 30 Sept 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-103932
- GitHub Advisory Database https://github.com/advisories/GHSA-5m93-4h75-3p2w
- github.com https://github.com/owasp-modsecurity/ModSecurity/security/advisories/GHSA-5m93-4h75-3p2w