← back

CVE-2026-21876

CRITICAL · 9.3 EPSS 0.1%
hype MOSTLY HYPE · 28 hack

Real vuln with patches shipped, but no PoC, no KEV, recycled patch announcements dominate chatter.

What: Logic bug in OWASP CRS rule 922110 allowing multipart requests with malicious charsets in early parts to bypass detection if later parts contain legitimate charsets (CVSS 9.3 CRITICAL). Affects CRS <4.22.0 and <3.3.8.

Why it matters: Patches released (CRS 4.22.0 and 3.3.8); vendor actively addressing. High CVSS reflects WAF bypass potential. No KEV listing, no public PoC confirmed in posts, no in-the-wild exploitation reports yet. Chatter is primarily patch notification, not exploitation discussion.

Where it's seen: Repetitive social posts (mostly same account variants) announcing patch availability. Appears to be coordinated awareness campaign rather than organic security community reaction. No defender triage questions or PoC repositories mentioned.

RISK: HIGH — Critical CVSS, WAF bypass affects cloud/enterprise deployments, patches available but adoption lag risk.

Generated by claude-haiku-4-5 from public posts and authoritative metadata. AI can make mistakes — verify against vendor advisories before acting. 5/2/2026, 1:24:21 AM

The OWASP core rule set (CRS) is a set of generic attack detection rules for use with compatible web application firewalls. Prior to versions 4.22.0 and 3.3.8, the current rule 922110 has a bug when processing multipart requests with multiple parts. When the first rule in a chain iterates over a collection (like `MULTIPART_PART_HEADERS`), the capture variables (`TX:0`, `TX:1`) get overwritten with each iteration. Only the last captured value is available to the chained rule, which means malicious charsets in earlier parts can be missed if a later part has a legitimate charset. Versions 4.22.0 and 3.3.8 patch the issue.

Public PoCs on GitHub 5 repos

Articles & coverage 15 articles

Page 1 of 3
NVD details 1 CWE ·1 vendor · 6 refs expand

Description

The OWASP core rule set (CRS) is a set of generic attack detection rules for use with compatible web application firewalls. Prior to versions 4.22.0 and 3.3.8, the current rule 922110 has a bug when processing multipart requests with multiple parts. When the first rule in a chain iterates over a collection (like `MULTIPART_PART_HEADERS`), the capture variables (`TX:0`, `TX:1`) get overwritten with each iteration. Only the last captured value is available to the chained rule, which means malicious charsets in earlier parts can be missed if a later part has a legitimate charset. Versions 4.22.0 and 3.3.8 patch the issue.

Weaknesses

Vendors

  • owasp

Products

  • owasp_modsecurity_core_rule_set

References

Top posts driving the trend