Read the docs

OWASP CRS rules miss attacks hidden in XML attribute values

Priority HIGH 71CWE-138Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

The OWASP Core Rule Set (coreruleset) before 3.3.10, before 4.25.1 and before 4.28.0 inspects XML request bodies only through the XPath expression XML:/*, which matches element text nodes but not attribute values (CWE-138). An unauthenticated remote attacker can place an attack payload inside an XML attribute, which bypasses detection by about 159 rules across nine rule families at every paranoia level. The 944 (Java) family is not affected because it also inspects XML attributes.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

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, CRS rules in the 921 (protocol-attack), 930 (LFI), 931 (RFI), 932 (RCE), 933 (PHP), 934 (generic), 941 (XSS), 942 (SQLi), and 943 (session-fixation) families inspect XML request bodies via the XPath expression XML:/*. That expression matches only element text nodes — it does not match XML attribute values. As a result, an attacker who places an attack payload inside an XML attribute (e.g. <a href="javascript:alert(1)=window.name"></a> or <a value="' OR 1=1 --"></a>) bypasses CRS detection entirely. This is verified empirically against a local CRS test instance and against the public CRS sandbox. The bypass affects approximately 159 rules across 9 rule files and applies at every paranoia level (PL1 through PL4), since the variable list is more or less shared across PLs. The 944 (Java) family is the only one that correctly includes XML://@* in addition to XML:/* and is therefore unaffected. This issue has been patched in versions 3.3.10, 4.25.1, and 4.28.0.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00425 37th percentileScored 2026-11-16
Fix Fixed coreruleset (coreruleset): 3.3.10, 4.25.1, 4.28.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
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

VendorProductAffected versionsFixed inStatusSource
corerulesetcorerulesetbefore 3.3.10; before 4.25.1; before 4.28.03.3.10, 4.25.1, 4.28.0Patch availableCNA
  • 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 version 3.3.10, 4.25.1 or 4.28.0, matching the release line in use.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA coreruleset (coreruleset) Fixed in 3.3.10, 4.25.1, 4.28.0

Timeline

  1. 2026-11-11 Threatist record created from CVE-2026-62971
  2. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2026-89849 ReDoS in OWASP Core Rule Set Unix RCE rules enables detection bypass CVSS 4.0HIGH 8.8

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences