ReDoS in OWASP Core Rule Set Unix RCE rules enables detection bypass
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · Low · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-1333.
Summary
OWASP Core Rule Set (coreruleset) is affected before 3.3.10, before 4.25.1 and before 4.28.0. A shared regex-assembly include used by 12 Unix RCE detection rules in CRS v4, and manually assembled regexes in 4 rules in CRS v3.3, contain an ambiguous pattern that causes ReDoS (CWE-1333). A single unauthenticated crafted request drives PCRE2 past its backtracking limit, so the @rx operator returns an error instead of a match, which bypasses detection and causes CPU denial of service.
Written with Claude Haiku 5.5 from the sources below · 2026-11-11
Description from the CNA
The OWASP core rule set (CRS) is a set of generic attack detection rules for use with compatible web application firewalls. Prior to versions 3.3.10, 4.25.1, and 4.28.0, regular-expression denial of service (ReDoS) affects a shared regex-assembly include used to build 12 Unix RCE detection rules in CRS v4, and the same ambiguous pattern was present in the manually-assembled regexes in 4 rules in CRS v3.3. With a single, unauthenticated, crafted request, the generated pattern drives PCRE2 past its backtracking limit. When PCRE2 exceeds that limit, the @rx operator returns an error rather than a match result, which results in detection bypass and CPU denial of service. This issue has been patched in versions 3.3.10, 4.25.1, and 4.28.0.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| coreruleset | coreruleset | before 3.3.10; before 4.25.1; before 4.28.0 | 3.3.10, 4.25.1, 4.28.0 | Patch available | CNA |
- coreruleset Vendorcoreruleset Affected before 3.3.10; before 4.25.1; before 4.28.0 Fixed in 3.3.10, 4.25.1, 4.28.0 Patch available CNA
Remediation
Update coreruleset to 3.3.10, 4.25.1 or 4.28.0, which fix this issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-11
- Fix · CNA coreruleset (coreruleset) Fixed in 3.3.10, 4.25.1, 4.28.0
Timeline
- 2026-11-11 Threatist record created from CVE-2026-61619
- 2026-11-12 CISA SSVC decision points changed
References
Other 4
- https://github.com/coreruleset/coreruleset/security/advisories/GHSA-f5qm-3h4p-8qhg
- https://github.com/coreruleset/coreruleset/commit/4665b6d7a79a81aa8a802ef3c901d69491c009a4
- https://github.com/coreruleset/coreruleset/commit/6083611d00291e85ab7b587e96577deb53ed9cac
- https://github.com/coreruleset/coreruleset/commit/e3b612a909532dcc8d056c01ac04b31117b71505
More coreruleset vulnerabilities
- TI-2026-89844 OWASP CRS rules miss attacks hidden in XML attribute values CVSS 3.1HIGH 7.2
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences