Vulnerability Database · Go · Package report

github.com/jptosso/coraza-waf: vulnerability history, versions and safety

github.com/jptosso/coraza-waf is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 97 releases, first recorded in Mar 2025. 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 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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.

Vulert verdict on github.com/jptosso/coraza-waf v1.2.0 i

Updated on 23 Oct 2026

Action needed: v1.2.0 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 77/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v1.2.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 20 Mar 2025 i
  • Highest CVSS 5.4 i
  • With no published fix 0 i
  • Stars 3,922 i
  • OpenSSF scorecard 7/10 i
  • Last release 61 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/jptosso/coraza-waf, 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
v1.2.1-0.20211119154908-89239d658eef 19 Nov 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20211117033756-8aaa7bca52bf 17 Nov 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20211116144024-715a2ce09904 16 Nov 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20211105185728-f26fca408cd6 05 Nov 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20211020115446-bd6c13b6d560 20 Oct 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20211019015706-90ce84f7d185 19 Oct 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20211015184458-1948a6780be7 15 Oct 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210928132100-0b4d0fdbebd9 28 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210921222957-2a028a037708 21 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210920152926-02221edad47a 20 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210920024209-c474b319eef0 20 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210919152653-4d9247e47cd6 19 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210919134930-f6a3436bd486 19 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210919134641-80ca72b6898b 19 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210919134404-7b5bb5a82d40 19 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210917142149-3b5a9b9514ea 17 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210917141303-9ae0e48f6cd0 17 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210917023802-3629ecd1838c 17 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210917020846-7e8e91f59eb6 17 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210916173658-7b409acfefc4 16 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210916173539-a3086dbeb922 16 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210916173314-38a6091b137c 16 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.1-0.20210913184650-5d9ad82a85b7 13 Sep 2021 M1 Apache-2.0 Yes Details →
v1.2.0 10 Sep 2021 M1 Apache-2.0 Yes Details →
v1.1.1-0.20210910143654-5399ee346cea 10 Sep 2021 M1 Apache-2.0 Yes Details →
v1.1.1-0.20210910011153-fbf2fa85c22a 10 Sep 2021 M1 Apache-2.0 Yes Details →
v1.1.1-0.20210909223838-fcd8722c4ee7 09 Sep 2021 M1 Apache-2.0 Yes Details →
v1.1.1-0.20210909205218-245862d57b35 09 Sep 2021 M1 Apache-2.0 Yes Details →
v1.1.1-0.20210909195341-0a75bf898af8 09 Sep 2021 M1 Apache-2.0 Yes Details →
v1.1.1-0.20210907221151-34e896c169b8 07 Sep 2021 M1 Apache-2.0 Yes Details →
v1.1.0 06 Sep 2021 M1 Apache-2.0 Yes Details →
v1.0.1-0.20210903211842-c0da04def4c8 03 Sep 2021 M1 Apache-2.0 Yes Details →
v1.0.0 01 Sep 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.7.0.20210901000958-dfa21cbd43df 01 Sep 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.7.0.20210827014205-b83420496d8a 27 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.6.0.20210827002432-fc2e9d7a37b1 27 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.7 27 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.6.0.20210827001052-3e9855358bb3 27 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.6.0.20210826215553-5b81b8a6aecc 26 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.5.0.20210825211754-fc63d67c7b64 25 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.6 25 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.5.0.20210825025520-2dbeb395a91b 25 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.4.0.20210823000347-2b2b7061e26b 23 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.5 23 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.3.0.20210821060604-f77c1bd1dd48 21 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.4 21 Aug 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210821060224-7441b9591f11 21 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.2.0.20210818022021-879cf8486d69 18 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.3 18 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.2.0.20210811231425-ca0d9f177220 11 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.1.0.20210809215317-e45ecda9e6d1 09 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.2 09 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.1.0.20210807004546-bbb8c415c8b1 07 Aug 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.1.0.20210801022604-33f790c2f90b 01 Aug 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210729014056-6ce53c5bcdfa 29 Jul 2021 M1 Apache-2.0 Yes Details →
v1.0.0-beta.1 29 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210723013340-144ee694e249 23 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210722092813-264871fc6ab1 22 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210722091624-803c05c6824d 22 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210722090739-5d45c242af75 22 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210721231810-9449c5f3859c 21 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210721221328-cac13a769a9c 21 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210721004206-692e8fd6de90 21 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210720080623-81ff10503710 20 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210720005144-a7de0660cfe5 20 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210714205438-1e75eff8a06c 14 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210714151411-2916f44dc3ee 14 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210713145329-64a279f4cdbc 13 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210712221901-710f33f40a75 12 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210711154807-1342f09e3cdc 11 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210622223802-db7e4bddd2fe 22 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210621181955-69d173627e42 21 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210621161123-a45d72089851 21 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210621001436-9b6abcedfb0d 21 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210612014543-161d7f4a16f7 12 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210610013611-fc0bdf2e3a24 10 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210609221250-fbd5935609b5 09 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210606183212-f3fafa035454 06 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210606164753-db43e1e49302 06 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210606163617-20490e861bd8 06 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210606152650-94ed79b9c024 06 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210603034709-b9c5f88da88b 03 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210603022639-600623287413 03 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210603014949-f702ee49a9fa 03 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210602225256-bae7549f5eb8 02 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210601015932-98456f137580 01 Jun 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210521213248-67ee1b2bfdf2 21 May 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210521211624-bf46275160ac 21 May 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210508183545-a40d5a3809c5 08 May 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20201024230055-ff9c8f04d0bf 24 Oct 2020 M1 Apache-2.0 Yes Details →
v0.0.0-20200920015851-d91752d845b6 20 Sep 2020 M1 Apache-2.0 Yes Details →
v0.0.0-20200917192351-04608f84acc5 17 Sep 2020 M1 Apache-2.0 Yes Details →
v0.0.0-20200917165434-e72e2ba67b2a 17 Sep 2020 M1 Apache-2.0 Yes Details →
v0.0.0-20200915003202-2415c6fddcda 15 Sep 2020 M1 Apache-2.0 Yes Details →
v0.0.0-20200818222209-d892d309b807 18 Aug 2020 M1 Apache-2.0 Yes Details →
v0.0.0-20200808211259-0db1b1e28302 08 Aug 2020 M1 Apache-2.0 Yes Details →
v0.0.0-20200527171008-734a598ca30c 27 May 2020 M1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 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/jptosso/coraza-waf

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

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/jptosso/coraza-waf

Is github.com/jptosso/coraza-waf safe to use?

Vulert records 1 vulnerabilities for github.com/jptosso/coraza-waf in Go: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/jptosso/coraza-waf's Vulert package health score?

Vulert scores github.com/jptosso/coraza-waf 77/100, which reads as in good shape. 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).

Is the latest version of github.com/jptosso/coraza-waf affected?

Yes. v1.2.0, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/jptosso/coraza-waf should I use?

v1.2.0 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/jptosso/coraza-waf have?

1 vulnerability is recorded for github.com/jptosso/coraza-waf in the Go ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/jptosso/coraza-waf vulnerabilities disclosed?

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

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