VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

github.com/corazawaf/coraza/v2 is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 40 releases, first recorded in Jul 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
i
1 with no fix published

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

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

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/corazawaf/coraza/v2 vulnerabilities

Vulert verdict on github.com/corazawaf/coraza/v2 v2.0.1 i

Updated on 23 Oct 2026

Careful: v2.0.1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v2.0.1 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 05 Jul 2023 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Stars 3,913 i
  • OpenSSF scorecard 8/10 i
  • Last release 50 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

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

Every version Vulert tracks for github.com/corazawaf/coraza/v2, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v2.0.2-0.20221003085423-ed447402a0b7 03 Oct 2022 U1 Apache-2.0 No Details →
v2.0.2-0.20220905134927-f95f41d9b0a2 05 Sep 2022 U1 Apache-2.0 No Details →
v2.0.2-0.20220811005045-724d2bcdbf84 11 Aug 2022 U1 Apache-2.0 No Details →
v2.0.2-0.20220726002511-30f000aff7ca 26 Jul 2022 U1 Apache-2.0 No Details →
v2.0.1 25 Jul 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220722105224-abb8f0300623 22 Jul 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220717185046-e58bb79ebf4f 17 Jul 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220713215206-46a8f259b194 13 Jul 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220713155407-1495cc9cae4a 13 Jul 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220711132720-4866c0ccda8f 11 Jul 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220617082956-b14dbef408b0 17 Jun 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220615145123-6498620c34ce 15 Jun 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220615022252-7ab17dbe6861 15 Jun 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220611152940-0502bb907439 11 Jun 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220429021649-f8e930d3a06a 29 Apr 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220428140515-226ee62c6ab0 28 Apr 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220425143600-46a986ad8c35 25 Apr 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220422070717-7013ac4bd779 22 Apr 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220421204936-058ef8c91908 21 Apr 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220421195046-2698c687d2f0 21 Apr 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220421161233-c350d77b3969 21 Apr 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220419154408-f257ca6f6b11 19 Apr 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220418025101-0bc8f784eae6 18 Apr 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220414200730-e90d75878a10 14 Apr 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220414094650-1253189fc166 14 Apr 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220413141959-9c36e4dd40b0 13 Apr 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220411151331-b92349ba953b 11 Apr 2022 U1 Apache-2.0 No Details →
v2.0.1-0.20220401022042-958973479455 01 Apr 2022 U1 Apache-2.0 No Details →
v2.0.0 22 Mar 2022 U1 Apache-2.0 No Details →
v2.0.0-rc.3.0.20220322211430-fdad9f5e07fb 22 Mar 2022 U1 Apache-2.0 No Details →
v2.0.0-rc.3.0.20220321140609-19d59b29a289 21 Mar 2022 U1 Apache-2.0 No Details →
v2.0.0-rc.3.0.20220317111206-0b93154e43d1 17 Mar 2022 U1 Apache-2.0 No Details →
v2.0.0-rc.3.0.20220317021837-895ea13224b2 17 Mar 2022 U1 Apache-2.0 No Details →
v2.0.0-rc.2.0.20220310182130-62dd3db3f725 10 Mar 2022 U1 Apache-2.0 No Details →
v2.0.0-rc.3 10 Mar 2022 U1 Apache-2.0 No Details →
v2.0.0-rc.2.0.20220308140246-a6ef8076b1c0 08 Mar 2022 U1 Apache-2.0 No Details →
v2.0.0-rc.2.0.20220302145703-5c659854c6a6 02 Mar 2022 U1 Apache-2.0 No Details →
v2.0.0-rc.2.0.20220227125605-ff4248c481a6 27 Feb 2022 U1 Apache-2.0 No Details →
v2.0.0-rc.2.0.20220224143848-e9b65b57e2ba 24 Feb 2022 U1 Apache-2.0 No Details →
v2.0.0-rc.2.0.20220217154443-1fe2547b3fd0 17 Feb 2022 U1 Apache-2.0 No Details →

All 40 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/corazawaf/coraza/v2

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-1874: Denial of service in github.com/corazawaf/coraza/v2 and v3 N/A unrated No fix published 05 Jul 2023

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/v2

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

Vulert records 1 vulnerabilities for github.com/corazawaf/coraza/v2 in Go: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is github.com/corazawaf/coraza/v2's Vulert package health score?

Vulert scores github.com/corazawaf/coraza/v2 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/corazawaf/coraza/v2 affected?

Yes. v2.0.1, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/corazawaf/coraza/v2 should I use?

v2.0.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

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

1 vulnerability is recorded for github.com/corazawaf/coraza/v2 in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 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/v2 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/corazawaf/coraza/v2 in the last 12 months, and the oldest entry in this database dates to 05 Jul 2023. 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/v2 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/v2 for upcoming vulnerabilities?

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