CVE-2026-41510 affects Coraza versions 3.0.0 through 3.8.0. Incomplete argument-limit enforcement silently drops arguments from inspection, allowing parameter flooding to conceal malicious payloads from ARGS-targeted web application firewall rules. Incomplete parsing limits and JSON-flattening byte-budget enforcement also permit excessive resource consumption. Affected processing includes URL-encoded arguments, repeated keys, nested JSON array-length entries, and JSON response bodies processed through RESPONSE_ARGS. Version 3.8.0 contains an incomplete fix; version 3.8.1 completes the remediation.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Coraza silently discards arguments exceeding SecArgumentsLimit without signaling incomplete inspection, allowing parameter flooding to hide malicious payloads from ARGS-targeted WAF rules. The advisory also covers unenforced argument limits, repeated-key counting gaps, and JSON flattening amplification that can exhaust memory and increase CPU consumption. Public proofs of concept demonstrate WAF bypass and memory amplification. Versions 3.0.0 through 3.8.0 are affected; 3.8.1 completes the fix. The revised severity is CVSS 3.1 High, 7.2.
A high-severity vulnerability affecting github.com/corazawaf/coraza/v3. Its CVSS v3 score is 7.2, indicating network-based exploitation without authentication or user interaction, with low integrity and availability impacts. The content does not describe the specific vulnerability mechanism. Version 3.8.1 or later addresses the issue.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.