No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 10 Nov 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 06 Nov 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-393 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Thu, 05 Nov 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Modsecurity
Modsecurity modsecurity |
|
| Vendors & Products |
Modsecurity
Modsecurity modsecurity |
Thu, 05 Nov 2026 15:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | ModSecurity: PCRE2 `@rxGlobal` match-limit errors are converted to no-match | |
| Weaknesses | CWE-253 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-11-09T17:14:29.857Z
Reserved: 2026-10-01T14:20:19.156Z
Link: CVE-2026-103932
Updated: 2026-11-09T17:14:24.898Z
Status : Awaiting Analysis
Published: 2026-11-05T16:17:24.900
Modified: 2026-11-12T22:18:35.610
Link: CVE-2026-103932
OpenCVE Enrichment
Updated: 2026-11-06T13:30:05Z