Skip to main content
VulnerabilityPublished

CVE-2026-103932: ModSecurity · PCRE2 `@rxGlobal` match-limit errors are converted to no-match

Affects modsecurity2Source GCVE Database

0
Compare
Authoritative record:CVE-2026-103932· Medium 5.8

Not known to be exploited · CVSS 5.8 Medium : upgrade to 3.0.17 when convenient.

Data as of 17 Nov 2026, 16:34 UTC

CVSS 3.1 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.8
Patch
Available – fixed in 3.0.17
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade modsecurity2 to 3.0.17.

Affected software

ProductAffectedFixed in
Bitnamimodsecurity2pkg:bitnami/modsecurity2Other threatsAffected
  • >=3.0.5 <3.0.17
Fixed in
  • 3.0.17

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade ModSecurity to version 3.0.17 or later, where this issue is fixed. Since a patch is available and the vulnerability is addressed in the fixed version, applying the official update is the recommended remediation.

Description

A vulnerability in ModSecurity versions 3.0.5 through 3.0.16 causes PCRE2 @rxGlobal match-limit errors to be treated as no-match results rather than errors. This behavior can allow attacker-controlled input to exhaust the SecPcreMatchLimit, preventing certain rules from executing and potentially allowing malicious requests to bypass the WAF. The issue is fixed in version 3.0.17.

References

Community reviews

Loading reviews…