Vulnerability Database · Go · Package report
github.com/go-chi/cors: vulnerability history, versions and safety
github.com/go-chi/cors is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/go-chi/cors v1.2.2 i
Updated on 23 Oct 2026
Good news: v1.2.2, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Niche
- Community Quiet
What to do: Stay on v1.2.2 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.2.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.2.2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 424 i
- OpenSSF scorecard 3/10 i
- Last release 15 months ago i
- Licence MIT 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/go-chi/cors, 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.
- v1.2.3-0.20261008123855-28a71e8bd43f 08 Oct 2026
- v0.0.0-20250701140642-3a5381283113 01 Jul 2025
- v1.2.2 01 Jul 2025
- v1.2.2-0.20240504093523-f8fbaeea0479 04 May 2024
- v1.2.2-0.20240504092404-b41f76786054 04 May 2024
- v1.2.2-0.20231112031453-76ca79794e02 12 Nov 2023
- v1.2.2-0.20230310203205-9aca6170f98f 10 Mar 2023
- v1.2.1 19 Apr 2022
- v1.2.1-0.20220419114447-1c9ca72198a8 19 Apr 2022
- v1.2.1-0.20220419112817-318c905bbaf3 19 Apr 2022
- v1.2.1-0.20210325123801-9b0b248d5e6b 25 Mar 2021
- v1.2.0 25 Mar 2021
- v1.1.2-0.20210307172151-f53767659fa6 07 Mar 2021
- v1.1.1 12 Apr 2020
- v1.1.0 11 Apr 2020
- v0.0.0-20180816152345-07727c846d14 16 Aug 2018
- v1.0.1 16 Aug 2018
- v1.0.1-0.20180816152345-07727c846d14 16 Aug 2018
- v0.0.0-20180726201812-e87e85b7b590 26 Jul 2018
- v1.0.0 02 Aug 2017
- v0.0.0-20170728014451-fa724686d452 28 Jul 2017
- v0.0.0-20161025151409-6ad15f4e1489 25 Oct 2016
All 22 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
03 Vulnerabilities
Recorded vulnerabilities for github.com/go-chi/cors
No vulnerabilities match this view.
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
Questions
About github.com/go-chi/cors
Is github.com/go-chi/cors safe to use?
Vulert has no vulnerabilities on record for github.com/go-chi/cors in Go at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is github.com/go-chi/cors's Vulert package health score?
Vulert scores github.com/go-chi/cors 65/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).
Is the latest version of github.com/go-chi/cors affected?
No. v1.2.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
Which version of github.com/go-chi/cors should I use?
v1.2.2 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/go-chi/cors have?
0 vulnerabilities are recorded for github.com/go-chi/cors in the Go ecosystem: 0 critical, 0 high, 0 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/go-chi/cors vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/go-chi/cors in the last 12 months. 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/go-chi/cors 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/go-chi/cors for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/go-chi/cors version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.