Vulnerability Database · Go · Package report

github.com/vulsio/go-exploitdb: vulnerability history, versions and safety

github.com/vulsio/go-exploitdb is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

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/vulsio/go-exploitdb v0.7.2 i

Updated on 23 Oct 2026

Good news: v0.7.2, the version you would install today, has no known vulnerabilities.

Package health score 71/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on v0.7.2 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.7.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.7.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 307 i
  • OpenSSF scorecard 4/10 i
  • Last release 5 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/vulsio/go-exploitdb, 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.7.3-0.20260512022205-eeb116a2113a 12 May 2026 none MIT — Details →
v0.7.2 11 May 2026 none MIT — Details →
v0.7.1 11 May 2026 none MIT — Details →
v0.7.1-0.20260424093844-902154778e77 24 Apr 2026 none MIT — Details →
v0.7.1-0.20260210030330-c474b70f3a09 10 Feb 2026 none MIT — Details →
v0.7.0 03 Feb 2026 none MIT — Details →
v0.6.4-0.20251215082522-6ddff63f51a1 15 Dec 2025 none MIT — Details →
v0.6.3 08 Dec 2025 none MIT — Details →
v0.6.2 24 Sep 2025 none MIT — Details →
v0.6.2-0.20250823055305-e484e69f84cd 23 Aug 2025 none MIT — Details →
v0.6.1 01 Jul 2025 none MIT — Details →
v0.6.0 24 Jun 2025 none MIT — Details →
v0.5.1-0.20250317025710-90df4972d112 17 Mar 2025 none MIT — Details →
v0.5.1-0.20241030125141-7d2fc13a9f55 30 Oct 2024 none MIT — Details →
v0.4.7-0.20240927064630-245f13318e79 27 Sep 2024 none MIT — Details →
v0.5.0 27 Sep 2024 none MIT — Details →
v0.4.7-0.20240704073305-1d9c13d7fc7c 04 Jul 2024 none MIT — Details →
v0.4.7-0.20240424061330-39155777f9a2 24 Apr 2024 none MIT — Details →
v0.4.7-0.20240318122115-ccb3abc151a1 18 Mar 2024 none MIT — Details →
v0.4.7-0.20240220162735-f70fd347a380 20 Feb 2024 none MIT — Details →
v0.4.7-0.20240208113139-5ef470b8e9ff 08 Feb 2024 none MIT — Details →
v0.4.7-0.20240108165657-f3bb489d3a00 08 Jan 2024 none MIT — Details →
v0.4.7-0.20231217192631-346af29403f1 17 Dec 2023 none MIT — Details →
v0.4.7-0.20231017104626-201191637c48 17 Oct 2023 none MIT — Details →
v0.4.6 06 Sep 2023 none MIT — Details →
v0.4.6-0.20230719132826-c053ddec9353 19 Jul 2023 none MIT — Details →
v0.4.6-0.20230622074051-f7bcf0f353a8 22 Jun 2023 none MIT — Details →
v0.4.5 10 May 2023 none MIT — Details →
v0.4.5-0.20230427040823-ffc725ef92eb 27 Apr 2023 none MIT — Details →
v0.4.5-0.20230426195811-b82ae91ae2d3 26 Apr 2023 none MIT — Details →
v0.4.4 22 Feb 2023 none MIT — Details →
v0.4.4-0.20230222062951-259497afef14 22 Feb 2023 none MIT — Details →
v0.4.3 19 Feb 2023 none MIT — Details →
v0.4.3-0.20221125095532-4d40a8e58e45 25 Nov 2022 none MIT — Details →
v0.4.3-0.20220627020833-7bfd613eb733 27 Jun 2022 none MIT — Details →
v0.4.3-0.20220325202050-142d5e45adb0 25 Mar 2022 none MIT — Details →
v0.4.2 24 Mar 2022 none MIT — Details →
v0.4.2-0.20220106203806-694e67827c1e 06 Jan 2022 none MIT — Details →
v0.4.2-0.20220106001533-dfbfaf40d5d1 06 Jan 2022 none MIT — Details →
v0.4.2-0.20211226000006-ae0f31046f91 26 Dec 2021 none MIT — Details →
v0.4.2-0.20211028071949-1ebf9c4f6c4d 28 Oct 2021 none MIT — Details →
v0.4.2-0.20211003233055-f8c6979e23e5 03 Oct 2021 none MIT — Details →
v0.4.2-0.20211001121417-3c58fdc07827 01 Oct 2021 none MIT — Details →
v0.4.2-0.20210930235136-c10d2716b7e2 30 Sep 2021 none MIT — Details →
v0.4.2-0.20210930011714-10b78a3740a9 30 Sep 2021 none MIT — Details →
v0.4.2-0.20210922110533-71f38da1d9bb 22 Sep 2021 none MIT — Details →
v0.4.1 22 Sep 2021 none MIT — Details →
v0.4.0 16 Sep 2021 none MIT — Details →
v0.3.0 01 Sep 2021 none MIT — Details →
v0.2.0 19 Aug 2021 none MIT — Details →
v0.0.0-20210625021845-e5081ca67229 25 Jun 2021 none MIT — Details →
v0.1.8-0.20210625021845-e5081ca67229 25 Jun 2021 none MIT — Details →
v0.1.8-0.20210621224002-ace20b83844f 21 Jun 2021 none MIT — Details →
v0.1.8-0.20210621214730-aab57769ab22 21 Jun 2021 none MIT — Details →
v0.1.7 23 Mar 2021 none MIT — Details →
v0.1.6 05 Mar 2021 none MIT — Details →
v0.1.5 04 Mar 2021 none MIT — Details →
v0.1.4 22 Jan 2021 none MIT — Details →
v0.1.3 22 Jan 2021 none MIT — Details →
v0.0.0-20190111121427-652ae1f6aa23 11 Jan 2019 none MIT — Details →
v0.0.0-20181130020745-7c961e736f7b 30 Nov 2018 none MIT — Details →

All 61 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/vulsio/go-exploitdb

No vulnerability write-ups match this view

Search all 0 in the database →

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

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/vulsio/go-exploitdb

Is github.com/vulsio/go-exploitdb safe to use?

Vulert has no vulnerabilities on record for github.com/vulsio/go-exploitdb 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/vulsio/go-exploitdb's Vulert package health score?

Vulert scores github.com/vulsio/go-exploitdb 71/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/vulsio/go-exploitdb affected?

No. v0.7.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/vulsio/go-exploitdb should I use?

v0.7.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/vulsio/go-exploitdb have?

0 vulnerabilities are recorded for github.com/vulsio/go-exploitdb 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/vulsio/go-exploitdb vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/vulsio/go-exploitdb 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/vulsio/go-exploitdb 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/vulsio/go-exploitdb for upcoming vulnerabilities?

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