VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/ntbosscher/gobase: vulnerability history, versions and safety

github.com/ntbosscher/gobase is a package in the Go ecosystem. Vulert records 4 vulnerabilities for it across 93 releases, from Feb 2022 to Dec 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded L2 U2
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/ntbosscher/gobase vulnerabilities

Vulert verdict on github.com/ntbosscher/gobase v0.12.2 i

Updated on 23 Oct 2026

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

Package health score 62/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • 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 v0.12.2 — affected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 28 Dec 2022 i
  • Highest CVSS 3.7 i
  • With no published fix 0 i
  • Stars 1 i
  • OpenSSF scorecard 1/10 i
  • Last release this month 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/ntbosscher/gobase, 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
v0.12.2 22 Oct 2026 L2 U2 — Yes Details →
v0.12.1 17 Sep 2026 L2 U2 — Yes Details →
v0.12.0 02 Sep 2026 L2 U2 — Yes Details →
v0.11.0 31 Aug 2026 L2 U2 — Yes Details →
v0.10.2 26 Aug 2026 L2 U2 — Yes Details →
v0.10.1 21 Aug 2026 L2 U2 — Yes Details →
v0.10.0 17 Aug 2026 L2 U2 — Yes Details →
v0.9.5 30 Jul 2026 L2 U2 — Yes Details →
v0.9.4 30 Jul 2026 L2 U2 — Yes Details →
v0.9.3 29 Jul 2026 L2 U2 — Yes Details →
v0.9.0 24 Jul 2026 L2 U2 — Yes Details →
v0.8.1 23 Jul 2026 L2 U2 — Yes Details →
v0.8.1-0.20260723161109-345f39fe35b0 23 Jul 2026 L2 U2 — Yes Details →
v0.7.20-0.20260723154635-261df5ddb53d 23 Jul 2026 L2 U2 — Yes Details →
v0.8.0 23 Jul 2026 L2 U2 — Yes Details →
v0.7.20-0.20260706205605-701dcd1c35df 06 Jul 2026 L2 U2 — Yes Details →
v0.7.20-0.20260624181731-2cb848756669 24 Jun 2026 L2 U2 — Yes Details →
v0.7.20-0.20260622163459-ee1d26b5d01e 22 Jun 2026 L2 U2 — Yes Details →
v0.7.20-0.20260615160317-a2299a6ac56c 15 Jun 2026 L2 U2 — Yes Details →
v0.7.20-0.20260521163709-0860c31deaef 21 May 2026 L2 U2 — Yes Details →
v0.7.20-0.20260513163939-e9540b940764 13 May 2026 L2 U2 — Yes Details →
v0.7.20-0.20260422130501-e7072d284f11 22 Apr 2026 L2 U2 — Yes Details →
v0.7.20-0.20260414131039-a0e86915f5de 14 Apr 2026 L2 U2 — Yes Details →
v0.7.20-0.20260413173036-12fa196d2aaa 13 Apr 2026 L2 U2 — Yes Details →
v0.7.20-0.20260413164918-70b6e1400127 13 Apr 2026 L2 U2 — Yes Details →
v0.7.20-0.20260413161819-4b6810f22c40 13 Apr 2026 L2 U2 — Yes Details →
v0.7.20-0.20260317173150-02b593c727c5 17 Mar 2026 L2 U2 — Yes Details →
v0.7.20-0.20260317164608-a525b11c4611 17 Mar 2026 L2 U2 — Yes Details →
v0.7.20-0.20260305155222-b53954b7a51b 05 Mar 2026 L2 U2 — Yes Details →
v0.7.20-0.20260305154354-64402e050bf4 05 Mar 2026 L2 U2 — Yes Details →
v0.7.20-0.20260107142409-b0333469935e 07 Jan 2026 L2 U2 — Yes Details →
v0.7.20-0.20251217142416-1c7c1ee3ee83 17 Dec 2025 L2 U2 — Yes Details →
v0.7.20-0.20251216154903-4d04fccb8952 16 Dec 2025 L2 U2 — Yes Details →
v0.7.20-0.20251216154601-8b95bd76f390 16 Dec 2025 L2 U2 — Yes Details →
v0.7.20-0.20251201160843-3e4e860c4c23 01 Dec 2025 L2 U2 — Yes Details →
v0.7.20-0.20251027132047-57f86a4bb342 27 Oct 2025 L2 U2 — Yes Details →
v0.7.20-0.20251014141120-3c056f1cf312 14 Oct 2025 L2 U2 — Yes Details →
v0.7.20-0.20251008145102-a4b820a9e7da 08 Oct 2025 L2 U2 — Yes Details →
v0.7.20-0.20251003181455-ca3cc51fc669 03 Oct 2025 L2 U2 — Yes Details →
v0.7.20-0.20251003181131-48a24a558d2b 03 Oct 2025 L2 U2 — Yes Details →
v0.7.20-0.20251003180304-f3b0ce04447f 03 Oct 2025 L2 U2 — Yes Details →
v0.7.20-0.20250905161234-3fec811f3799 05 Sep 2025 L2 U2 — Yes Details →
v0.7.20-0.20250827211050-022d5e2147f3 27 Aug 2025 L2 U2 — Yes Details →
v0.7.20-0.20250827210754-a5724c44e86e 27 Aug 2025 L2 U2 — Yes Details →
v0.7.20-0.20250827210300-6240c235cd18 27 Aug 2025 L2 U2 — Yes Details →
v0.7.20-0.20250827202413-7562979c87fc 27 Aug 2025 L2 U2 — Yes Details →
v0.7.20-0.20250819142948-506a1f0d00ec 19 Aug 2025 L2 U2 — Yes Details →
v0.7.20-0.20250815131655-c28423b1d74c 15 Aug 2025 L2 U2 — Yes Details →
v0.7.20-0.20250808180503-75db1f010d8f 08 Aug 2025 L2 U2 — Yes Details →
v0.7.20-0.20250721165545-25942f8f5eda 21 Jul 2025 L2 U2 — Yes Details →
v0.7.20-0.20250721165503-b2ae3e99570c 21 Jul 2025 L2 U2 — Yes Details →
v0.7.20-0.20250721164650-351762dbbb1c 21 Jul 2025 L2 U2 — Yes Details →
v0.7.20-0.20250721162704-3b9208fc55b9 21 Jul 2025 L2 U2 — Yes Details →
v0.7.20-0.20250702125700-739b04f9b33a 02 Jul 2025 L2 U2 — Yes Details →
v0.7.20-0.20250624143915-d071ef048375 24 Jun 2025 L2 U2 — Yes Details →
v0.7.20-0.20250617184021-074fbd97ecf4 17 Jun 2025 L2 U2 — Yes Details →
v0.7.20-0.20240117174821-6bb07bfd495d 17 Jan 2024 L2 U2 — Yes Details →
v0.7.20-0.20230825210926-cfa9fc6a99eb 25 Aug 2023 L2 U2 — Yes Details →
v0.7.20-0.20230721202733-5c8749f6f5cc 21 Jul 2023 L2 U2 — Yes Details →
v0.7.20-0.20230721200303-da52aaf6b9ab 21 Jul 2023 L2 U2 — Yes Details →
v0.7.20-0.20230721155623-3500eea82d91 21 Jul 2023 L2 U2 — Yes Details →
v0.7.20-0.20230721151348-01a747f25673 21 Jul 2023 L2 U2 — Yes Details →
v0.7.20-0.20230616204853-4f7535df9ac2 16 Jun 2023 L2 U2 — Yes Details →
v0.7.19 26 Apr 2022 L2 U2 — Yes Details →
v0.7.18 26 Jul 2021 L2 U2 — Yes Details →
v0.7.17 18 Dec 2020 L2 U2 — Yes Details →
v0.7.16 04 Dec 2020 L2 U2 — Yes Details →
v0.7.15 16 Nov 2020 L2 U2 — Yes Details →
v0.7.14 16 Nov 2020 L2 U2 — Yes Details →
v0.7.13 16 Nov 2020 L2 U2 — Yes Details →
v0.7.11 16 Nov 2020 L2 U2 — Yes Details →
v0.7.12 16 Nov 2020 L2 U2 — Yes Details →
v0.7.10 16 Nov 2020 L2 U2 — Yes Details →
v0.7.9 11 Nov 2020 L2 U2 — Yes Details →
v0.7.8 11 Nov 2020 L2 U2 — Yes Details →
v0.7.7 11 Nov 2020 L2 U2 — Yes Details →
v0.7.6 11 Nov 2020 L2 U2 — Yes Details →
v0.7.5 11 Nov 2020 L2 U2 — Yes Details →
v0.7.4 06 Nov 2020 L2 U2 — Yes Details →
v0.7.3 06 Nov 2020 L2 U2 — Yes Details →
v0.7.2 05 Nov 2020 L2 U2 — Yes Details →
v0.7.1 05 Nov 2020 L2 U2 — Yes Details →
v0.7.0 03 Nov 2020 L2 U2 — Yes Details →
v0.6.1 03 Nov 2020 L2 U2 — Yes Details →
v0.6.0 03 Nov 2020 L2 U2 — Yes Details →
v0.5.2 03 Nov 2020 L2 U2 — Yes Details →
v0.5.1 03 Nov 2020 L2 U2 — Yes Details →
v0.5.0 03 Nov 2020 L2 U2 — Yes Details →
v0.4.1 30 Oct 2020 L2 U2 — Yes Details →
v0.4.0 29 Oct 2020 L2 U2 — Yes Details →
v0.3.0 01 Oct 2020 L2 U2 — Yes Details →
v0.1.1-0.20200902191011-f5b9b6105f8c 02 Sep 2020 L2 U2 — Yes Details →
v0.1.0 28 Aug 2020 L2 U2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/ntbosscher/gobase

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Incorrect routing of HTTP requests in gobase when using httpauth 3.7 low 0.7.2 11 Feb 2022
CVE-2022-2583: GoBase Race Condition vulnerability 3.7 low 0.7.2 28 Dec 2022
CVE-2022-25839: Improper Input Validation in url-js N/A unrated 0.7.2 01 Jul 2022
CVE-2022-2583: Race condition in github.com/ntbosscher/gobase N/A unrated 0.7.2 01 Jul 2022

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/ntbosscher/gobase

Is github.com/ntbosscher/gobase safe to use?

Vulert records 4 vulnerabilities for github.com/ntbosscher/gobase in Go: 0 critical, 0 high, 0 medium and 2 low, plus 2 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/ntbosscher/gobase's Vulert package health score?

Vulert scores github.com/ntbosscher/gobase 62/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/ntbosscher/gobase affected?

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

How many vulnerabilities does github.com/ntbosscher/gobase have?

4 vulnerabilities are recorded for github.com/ntbosscher/gobase in the Go ecosystem: 0 critical, 0 high, 0 medium and 2 low, plus 2 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/ntbosscher/gobase vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/ntbosscher/gobase in the last 12 months, and the oldest entry in this database dates to 11 Feb 2022. 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/ntbosscher/gobase 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/ntbosscher/gobase for upcoming vulnerabilities?

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