VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/jub0bs/cors: vulnerability history, versions and safety

github.com/jub0bs/cors is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 81 releases, first recorded in May 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 U1
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.

See all github.com/jub0bs/cors vulnerabilities

Vulert verdict on github.com/jub0bs/cors v1.2.0 i

Updated on 23 Oct 2026

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

Package health score 72/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Inactive

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 2 over 1 year · 0 in the last year i
  • Latest disclosure 21 May 2024 i
  • Highest CVSS 9.3 i
  • With no published fix 0 i
  • Stars 225 i
  • Last release this month 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/jub0bs/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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v1.1.4-0.20261021042754-58f94db39a07 21 Oct 2026 C1 U1 MIT Yes Details →
v1.2.0 21 Oct 2026 C1 U1 MIT Yes Details →
v1.1.4-0.20261020145654-c495aa9b3e4b 20 Oct 2026 C1 U1 MIT Yes Details →
v1.1.3 28 Sep 2026 C1 U1 MIT Yes Details →
v1.1.3-0.20260928060706-73b2e61d0515 28 Sep 2026 C1 U1 MIT Yes Details →
v1.1.2 18 Sep 2026 C1 U1 MIT Yes Details →
v1.1.1 04 Sep 2026 C1 U1 MIT Yes Details →
v1.1.1-0.20260831140844-5c052ee62b16 31 Aug 2026 C1 U1 MIT Yes Details →
v1.1.0 19 Aug 2026 C1 U1 MIT Yes Details →
v1.0.5 15 Jul 2026 C1 U1 MIT Yes Details →
v1.0.4 11 Jun 2026 C1 U1 MIT Yes Details →
v1.0.3 22 May 2026 C1 U1 MIT Yes Details →
v1.0.2 01 May 2026 C1 U1 MIT Yes Details →
v1.0.2-0.20260423164524-3c8dedf5dd1c 23 Apr 2026 C1 U1 MIT Yes Details →
v1.0.1 23 Apr 2026 C1 U1 MIT Yes Details →
v1.0.0 07 Apr 2026 C1 U1 MIT Yes Details →
v0.14.0 03 Apr 2026 C1 U1 MIT Yes Details →
v0.13.6 26 Mar 2026 C1 U1 MIT Yes Details →
v0.13.5 23 Mar 2026 C1 U1 MIT Yes Details →
v0.13.4 13 Mar 2026 C1 U1 MIT Yes Details →
v0.13.3 12 Mar 2026 C1 U1 MIT Yes Details →
v0.13.2 27 Feb 2026 C1 U1 MIT Yes Details →
v0.13.1 25 Feb 2026 C1 U1 MIT Yes Details →
v0.13.0 20 Feb 2026 C1 U1 MIT Yes Details →
v0.12.2 19 Feb 2026 C1 U1 MIT Yes Details →
v0.12.1 12 Feb 2026 C1 U1 MIT Yes Details →
v0.12.0 12 Feb 2026 C1 U1 MIT Yes Details →
v0.11.1-0.20260205141757-9c3bf3b672ae 05 Feb 2026 C1 U1 MIT Yes Details →
v0.11.1-0.20260202090401-015128af7969 02 Feb 2026 C1 U1 MIT Yes Details →
v0.11.0 31 Jan 2026 C1 U1 MIT Yes Details →
v0.10.1-0.20260128134747-63864a43dd4d 28 Jan 2026 C1 U1 MIT Yes Details →
v0.10.1-0.20260127152608-fbdd1678934b 27 Jan 2026 C1 U1 MIT Yes Details →
v0.10.0 25 Jan 2026 C1 U1 MIT Yes Details →
v0.9.3-0.20260116201452-feb0330fd240 16 Jan 2026 C1 U1 MIT Yes Details →
v0.9.3-0.20260116112138-61148fd9d156 16 Jan 2026 C1 U1 MIT Yes Details →
v0.9.3-0.20260115135941-cb6f0209d00f 15 Jan 2026 C1 U1 MIT Yes Details →
v0.9.2 25 Oct 2025 C1 U1 MIT Yes Details →
v0.9.1 30 Sep 2025 C1 U1 MIT Yes Details →
v0.9.1-0.20250914105832-7813a9e8d3c8 14 Sep 2025 C1 U1 MIT Yes Details →
v0.9.0 07 Sep 2025 C1 U1 MIT Yes Details →
v0.8.1-0.20250814125907-dde5bc5aef05 14 Aug 2025 C1 U1 MIT Yes Details →
v0.8.0 13 Aug 2025 C1 U1 MIT Yes Details →
v0.7.0 14 Jun 2025 C1 U1 MIT Yes Details →
v0.6.0 10 Jun 2025 C1 U1 MIT Yes Details →
v0.5.9 26 Apr 2025 C1 U1 MIT Yes Details →
v0.5.9-0.20250426080815-e7324130a229 26 Apr 2025 C1 U1 MIT Yes Details →
v0.5.9-0.20250407092717-ee9394a55b9a 07 Apr 2025 C1 U1 MIT Yes Details →
v0.5.8 03 Apr 2025 C1 U1 MIT Yes Details →
v0.5.7 13 Mar 2025 C1 U1 MIT Yes Details →
v0.5.7-0.20250220103924-71fe78c203eb 20 Feb 2025 C1 U1 MIT Yes Details →
v0.5.7-0.20250219122621-ec22bec71353 19 Feb 2025 C1 U1 MIT Yes Details →
v0.5.6 18 Feb 2025 C1 U1 MIT Yes Details →
v0.5.6-0.20250217194627-4f699784bb12 17 Feb 2025 C1 U1 MIT Yes Details →
v0.5.6-0.20250217085558-93ef0f1aa3ae 17 Feb 2025 C1 U1 MIT Yes Details →
v0.5.5 13 Feb 2025 C1 U1 MIT Yes Details →
v0.5.5-0.20250213144501-acfddbf11897 13 Feb 2025 C1 U1 MIT Yes Details →
v0.5.5-0.20250213144305-c8ccdd252ca0 13 Feb 2025 C1 U1 MIT Yes Details →
v0.5.4 04 Feb 2025 C1 U1 MIT Yes Details →
v0.5.3 24 Jan 2025 C1 U1 MIT Yes Details →
v0.5.2 15 Jan 2025 C1 U1 MIT Yes Details →
v0.5.1 13 Jan 2025 C1 U1 MIT Yes Details →
v0.5.0 05 Jan 2025 C1 U1 MIT Yes Details →
v0.4.0 19 Dec 2024 C1 U1 MIT Yes Details →
v0.3.2-0.20240905131247-01a1b7821d5b 05 Sep 2024 C1 U1 MIT Yes Details →
v0.3.1 05 Sep 2024 C1 U1 MIT Yes Details →
v0.3.0 28 Aug 2024 C1 U1 MIT Yes Details →
v0.2.1-0.20240528154152-ecbf8742bcdb 28 May 2024 C1 U1 MIT Yes Details →
v0.2.1-0.20240519085458-c569a6b8ac72 19 May 2024 C1 U1 MIT Yes Details →
v0.2.1-0.20240508131252-5e40061f1984 08 May 2024 C1 U1 MIT Yes Details →
v0.2.0 08 May 2024 C1 U1 MIT Yes Details →
v0.1.3 02 May 2024 C1 U1 MIT Yes Details →
v0.1.3-0.20240502050618-63900fa17762 02 May 2024 C1 U1 MIT Yes Details →
v0.1.2 04 Apr 2024 C1 U1 MIT Yes Details →
v0.1.2-0.20240403174603-83ad7114e2fc 03 Apr 2024 C1 U1 MIT Yes Details →
v0.1.1 03 Apr 2024 C1 U1 MIT Yes Details →
v0.1.1-0.20240401052123-e5a25e5e846e 01 Apr 2024 C1 U1 MIT Yes Details →
v0.1.1-0.20240329174031-5efdafeae14c 29 Mar 2024 C1 U1 MIT Yes Details →
v0.1.1-0.20240325142755-573d2f57b676 25 Mar 2024 C1 U1 MIT Yes Details →
v0.1.1-0.20240325070645-d540b7a5ebd9 25 Mar 2024 C1 U1 MIT Yes Details →
v0.0.0-20240323083620-fb98511c31ab 23 Mar 2024 C1 U1 MIT Yes Details →
v0.1.0 23 Mar 2024 C1 U1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/jub0bs/cors

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CORS Middleware Allows Untrusted Origins in github.com/jub0bs/cors 9.3 critical 0.1.3 03 May 2024
CORS Middleware Allows Untrusted Origins in github.com/jub0bs/cors N/A unrated 0.1.3 21 May 2024

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/jub0bs/cors

Is github.com/jub0bs/cors safe to use?

Vulert records 2 vulnerabilities for github.com/jub0bs/cors in Go: 1 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 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/jub0bs/cors's Vulert package health score?

Vulert scores github.com/jub0bs/cors 72/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/jub0bs/cors affected?

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

How many vulnerabilities does github.com/jub0bs/cors have?

2 vulnerabilities are recorded for github.com/jub0bs/cors in the Go ecosystem: 1 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/jub0bs/cors vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/jub0bs/cors in the last 12 months, and the oldest entry in this database dates to 03 May 2024. 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/jub0bs/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/jub0bs/cors for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/jub0bs/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.