Loading vulnerability…
CVE-2026-41504 is a CRLF injection vulnerability in the Native audit-log formatter of Coraza versions 3.0.0 through 3.7.0. When Native formatting is used with Serial or Concurrent audit logging, attacker-controlled content is written without escaping carriage returns or line feeds. This permits forged lines within audit records, undermining their integrity and reliability. Request-body injection is reachable through the stock HTTP integration; header injection requires an integration that accepts unvalidated header bytes. JSON and OCSF audit-log formats are unaffected.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity vulnerability affecting the github.com/corazawaf/coraza/v3 library. The listed CVSS v3 base score is 5.8, indicating network-based exploitation without privileges or user interaction, with low integrity impact and changed scope. The reference lists CWE-117 and CWE-93 but does not explain the underlying flaw. A patch was published on October 6, 2026; version 3.8.0 or later is recommended.
Coraza's Native audit-log formatter writes attacker-controlled data without escaping carriage returns and newlines, allowing forged log lines, misleading attribution, disrupted SIEM correlation, and concealment of genuine incidents. The request-body vector is reachable through the stock HTTP integration; header vectors require integrations accepting unvalidated header values. Unpredictable per-transaction boundary prefixes limit full separate-session forgery but do not preserve individual record integrity. The affected package range identifies version 3.8.0 as fixed. Mitigations include switching to JSON or OCSF output, escaping unsafe characters, or encoding logged bodies.
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.