VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/corazawaf/coraza: vulnerability history, versions and safety

github.com/corazawaf/coraza is a package in the Go ecosystem. Vulert records 13 vulnerabilities for it across 1 affected range, from Mar 2025 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
13 vulnerabilities recorded U13
i
13 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
12 in the last 12 months

Most recent disclosure 20 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/corazawaf/coraza vulnerabilities

Vulert verdict on github.com/corazawaf/coraza i

Updated on 23 Oct 2026

Careful: 13 of the 13 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

Long-term outlook: usable, but needs attention 13 vulnerabilities on record across 1 year, 12 in the last year.

What to do: Plan around the 13 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 13 over 1 year · 12 in the last year i
  • Latest disclosure 20 Oct 2026 i
  • Highest CVSS n/a i
  • With no published fix 13 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
all releases, no fix published yet 13

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 12

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 12 of the 13 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/corazawaf/coraza

The 5 most severe of 13 vulnerabilities recorded for this package

Search all 13 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-107834: Coraza Multipart Body Processor Resource Exhaustion Vulnerability N/A unrated No fix published 19 Oct 2026
CVE-2026-107826: Coraza JSON Body Processor Unbounded-Depth Stack Overflow Vulnerability N/A unrated No fix published 19 Oct 2026
CVE-2026-107835: Cookie Parser Confusion in Coraza WAF N/A unrated No fix published 19 Oct 2026
CVE-2026-104774: Coraza WAF Bypass Due to Off-by-One Error in Octal Escape Handling N/A unrated No fix published 19 Oct 2026
JSON Key Collision Vulnerability in Coraza Package Allows Bypass of OWASP CRS Inspection N/A unrated No fix published 19 Oct 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/corazawaf/coraza

Is github.com/corazawaf/coraza safe to use?

Vulert records 13 vulnerabilities for github.com/corazawaf/coraza in Go: 0 critical, 0 high, 0 medium and 0 low, plus 13 not yet rated. 13 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does github.com/corazawaf/coraza have?

13 vulnerabilities are recorded for github.com/corazawaf/coraza in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 13 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/corazawaf/coraza vulnerabilities disclosed?

12 vulnerabilities were recorded for github.com/corazawaf/coraza in the last 12 months, and the oldest entry in this database dates to 25 Mar 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/corazawaf/coraza are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/corazawaf/coraza for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/corazawaf/coraza version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.