Vulnerability Database · Go · Package report

github.com/klauspost/cpuid: vulnerability history, versions and safety

github.com/klauspost/cpuid 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/klauspost/cpuid v1.3.1 i

Updated on 23 Oct 2026

Good news: v1.3.1, the version you would install today, has no known vulnerabilities.

Package health score 60/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Widely used
  • Community Quiet

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

  • Current release v1.3.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,219 i
  • OpenSSF scorecard 4/10 i
  • Last release 75 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/klauspost/cpuid, 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.0.0-20201208113849-aa268cd09e03 08 Dec 2020 none MIT — Details →
v1.3.2-0.20201208110519-b0c8da32393f 08 Dec 2020 none MIT — Details →
v1.3.2-0.20201208095035-43f4c4132609 08 Dec 2020 none MIT — Details →
v1.3.2-0.20201204115725-eae48960b223 04 Dec 2020 none MIT — Details →
v1.3.2-0.20201127150341-242d0b0aa207 27 Nov 2020 none MIT — Details →
v1.3.2-0.20201127143551-321795ade971 27 Nov 2020 none MIT — Details →
v1.3.2-0.20200812114333-c8c182007590 12 Aug 2020 none MIT — Details →
v1.3.2-0.20200716101413-fc8eb62d0b31 16 Jul 2020 none MIT — Details →
v1.3.1 06 Jul 2020 none MIT — Details →
v1.3.1-0.20200626104532-b47a6aa133a4 26 Jun 2020 none MIT — Details →
v0.0.0-20200601190652-deab41a65a4a 01 Jun 2020 none MIT — Details →
v1.3.1-0.20200601190652-deab41a65a4a 01 Jun 2020 none MIT — Details →
v1.3.0 01 Jun 2020 none MIT — Details →
v1.2.6-0.20200528090307-0b33da1ab554 28 May 2020 none MIT — Details →
v1.2.5 26 May 2020 none MIT — Details →
v1.2.5-0.20200512133143-7799af8a0632 12 May 2020 none MIT — Details →
v1.2.4 03 May 2020 none MIT — Details →
v1.2.3 24 Jan 2020 none MIT — Details →
v1.2.3-0.20200123081501-0202b0bdeb22 23 Jan 2020 none MIT — Details →
v1.2.3-0.20200122153438-1dd42db450ac 22 Jan 2020 none MIT — Details →
v1.2.3-0.20200110143533-12f28c642700 10 Jan 2020 none MIT — Details →
v1.2.3-0.20200108110229-e6afad73b29d 08 Jan 2020 none MIT — Details →
v1.2.3-0.20200108104545-e6df68cf4c33 08 Jan 2020 none MIT — Details →
v1.2.2 06 Nov 2019 none MIT — Details →
v1.2.2-0.20191106130511-5a626f7029c9 06 Nov 2019 none MIT — Details →
v1.2.2-0.20191101092923-c9295f40f095 01 Nov 2019 none MIT — Details →
v0.0.0-20190713094507-cf2ded4aa833 13 Jul 2019 none MIT — Details →
v1.2.2-0.20190713094507-cf2ded4aa833 13 Jul 2019 none MIT — Details →
v1.2.2-0.20190712005203-6357cd93ed08 12 Jul 2019 none MIT — Details →
v0.0.0-20190422095156-05a8198c0f5a 22 Apr 2019 none MIT — Details →
v1.2.1 22 Apr 2019 none MIT — Details →
v0.0.0-20190414092417-9f2b0508aa72 14 Apr 2019 none MIT — Details →
v0.0.0-20190110101622-0da02118eaa3 10 Jan 2019 none MIT — Details →
v1.2.1-0.20190110101622-0da02118eaa3 10 Jan 2019 none MIT — Details →
v0.0.0-20181111194502-c640019ed4bd 11 Nov 2018 none MIT — Details →
v1.2.1-0.20181111194502-c640019ed4bd 11 Nov 2018 none MIT — Details →
v0.0.0-20180405133222-e7e905edc00e 05 Apr 2018 none MIT — Details →
v1.2.0 05 Apr 2018 none MIT — Details →
v1.2.1-0.20180405133222-e7e905edc00e 05 Apr 2018 none MIT — Details →
v0.0.0-20180324085119-30e450625213 24 Mar 2018 none MIT — Details →
v0.0.0-20180102081000-ae832f27941a 02 Jan 2018 none MIT — Details →
v0.0.0-20171118205520-eae9b3e628d7 18 Nov 2017 none MIT — Details →
v0.0.0-20170728055534-ae7887de9fa5 28 Jul 2017 none MIT — Details →
v0.0.0-20160302075316-09cded8978dc 02 Mar 2016 none MIT — Details →
v0.0.0-20160219142657-2c698c6aef59 19 Feb 2016 none MIT — Details →
v0.0.0-20160106104451-349c67577817 06 Jan 2016 none MIT — Details →
v0.0.0-20151217020554-6a7c11683953 17 Dec 2015 none MIT — Details →
v0.0.0-20151214135548-ef30b903ef21 14 Dec 2015 none MIT — Details →
v0.0.0-20151213164707-7e73800de58e 13 Dec 2015 none MIT — Details →
v0.0.0-20151213101143-27e68e2dd281 13 Dec 2015 none MIT — Details →
v0.0.0-20151207155142-eebb3eacf323 07 Dec 2015 none MIT — Details →
v0.0.0-20151207155130-0d6d278e7ee1 07 Dec 2015 none MIT — Details →
v0.0.0-20151013075656-8d9fe9648674 13 Oct 2015 none MIT — Details →
v0.0.0-20150918124101-50eec7f95054 18 Sep 2015 none MIT — Details →
v0.0.0-20150825114145-c9fd3fcd8d33 25 Aug 2015 none MIT — Details →
v0.0.0-20150825083642-04fcc06f390a 25 Aug 2015 none MIT — Details →
v0.0.0-20150712171152-3b0816bb6cb6 12 Jul 2015 none MIT — Details →
v0.0.0-20150707234504-8c38f8b5e336 07 Jul 2015 none MIT — Details →
v0.0.0-20150707201536-0c3eb20b81d5 07 Jul 2015 none MIT — Details →
v0.0.0-20150624122745-3e5ffbec521f 24 Jun 2015 none MIT — Details →
v0.0.0-20150615103827-9c472e65d46f 15 Jun 2015 none MIT — Details →
v0.0.0-20150523105821-0623620f57ee 23 May 2015 none MIT — Details →
v0.0.0-20150518150548-5397828774e2 18 May 2015 none MIT — Details →
v0.0.0-20150504122131-4b7162de9e64 04 May 2015 none MIT — Details →
v0.0.0-20150428111841-15b06259be24 28 Apr 2015 none MIT — Details →
v0.0.0-20150424152408-13d1823e7b6c 24 Apr 2015 none MIT — Details →
v0.0.0-20150414142306-565abd654db9 14 Apr 2015 none MIT — Details →
v0.0.0-20150413170020-0691968e1c8d 13 Apr 2015 none MIT — Details →

All 68 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/klauspost/cpuid

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/klauspost/cpuid

Is github.com/klauspost/cpuid safe to use?

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

Vulert scores github.com/klauspost/cpuid 60/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/klauspost/cpuid affected?

No. v1.3.1, 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/klauspost/cpuid should I use?

v1.3.1 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/klauspost/cpuid have?

0 vulnerabilities are recorded for github.com/klauspost/cpuid 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/klauspost/cpuid vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/klauspost/cpuid 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/klauspost/cpuid 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/klauspost/cpuid for upcoming vulnerabilities?

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