Is CVE-2026-103932 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-103932 being exploited in the wild.

How severe is CVE-2026-103932?

Medium severity, with a CVSS score of 5.8, published 5 November 2026.

Which products and versions are affected?

OWASP Modsecurity 3.0.5 through 3.0.17.

Is there a fix for CVE-2026-103932?

Yes: fixed in 3.0.17. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-103932 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-103932?

Check whether you run OWASP Modsecurity at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-103932: ModSecurity @rxGlobal match-limit bypass

CVE-2026-103932 · Severity: medium · CVSS 5.8 · Published 2026-11-05

ModSecurity is a web application firewall that protects web servers against attacks. Versions 3.0.5 through 3.0.17 fail to properly handle regex processing limits, allowing attackers to craft requests that exhaust the match limit and bypass security rules that should block malicious traffic. This could allow attacks that the firewall would normally detect and block to pass through.

Technologies: OWASP Modsecurity. Vendors: OWASP.

Quick answers

Is CVE-2026-103932 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-103932 being exploited in the wild.
How severe is CVE-2026-103932?: Medium severity, with a CVSS score of 5.8, published 5 November 2026.
Which products and versions are affected?: OWASP Modsecurity 3.0.5 through 3.0.17.
Is there a fix for CVE-2026-103932?: Yes: fixed in 3.0.17. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-103932 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-103932?: Check whether you run OWASP Modsecurity at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 3.0.17

Technical details

The PCRE2 implementation of the @rxGlobal operator in src/utils/regex.cc converts pcre2_match limit-exhaustion errors into no-match results instead of propagating the error, preventing compensating rules from triggering. An attacker can send requests with expressions designed to exhaust SecPcreMatchLimit, causing rules that check MSC_PCRE_LIMITS_EXCEEDED to skip execution. The vulnerability requires @rxGlobal with a limit-exhaustible expression and a compensating rule in the rule set.

Affected products

OWASP ModSecurity 3.0.5 through 3.0.17

Timeline

2026-11-05: disclosed
2026-09-29: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.