VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

stdlib: vulnerability history, versions and safety

stdlib is a package in the Go ecosystem. Vulert records 186 vulnerabilities for it across 120 releases, from Apr 2021 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
186 vulnerabilities recorded U186
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
61 in the last 12 months

Most recent disclosure 21 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all stdlib vulnerabilities

Vulert verdict on stdlib go1.25.5 i

Updated on 23 Oct 2026

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

Package health score 42/100
  • Security Unfixed issues
  • Maintenance Maintaining
  • Popularity Not enough data
  • Community Not enough data

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 go1.25.5 — affected i
  • Vulnerabilities on record 186 over 5 years · 61 in the last year i
  • Latest disclosure 21 Oct 2026 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 22 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 stdlib, 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
go1 — U169 BSD-3-Clause Yes Details →
go1.0.1 — U169 BSD-3-Clause Yes Details →
go1.0.2 — U169 BSD-3-Clause Yes Details →
go1.0.3 — U169 BSD-3-Clause Yes Details →
go1.1 — U169 BSD-3-Clause Yes Details →
go1.1.1 — U169 BSD-3-Clause Yes Details →
go1.1.2 — U169 BSD-3-Clause Yes Details →
go1.10 — U169 BSD-3-Clause Yes Details →
go1.10.1 — U169 BSD-3-Clause Yes Details →
go1.10.2 — U169 BSD-3-Clause Yes Details →
go1.10.3 — U169 BSD-3-Clause Yes Details →
go1.10.4 — U169 BSD-3-Clause Yes Details →
go1.10.5 — U169 BSD-3-Clause Yes Details →
go1.10.6 — U169 BSD-3-Clause Yes Details →
go1.10.7 — U169 BSD-3-Clause Yes Details →
go1.10.8 — U169 BSD-3-Clause Yes Details →
go1.10beta1 — U169 BSD-3-Clause Yes Details →
go1.10beta2 — U169 BSD-3-Clause Yes Details →
go1.10rc1 — U169 BSD-3-Clause Yes Details →
go1.10rc2 — U169 BSD-3-Clause Yes Details →
go1.11 — U169 BSD-3-Clause Yes Details →
go1.11.1 — U169 BSD-3-Clause Yes Details →
go1.11.10 — U169 BSD-3-Clause Yes Details →
go1.11.11 — U169 BSD-3-Clause Yes Details →
go1.11.12 — U169 BSD-3-Clause Yes Details →
go1.11.13 — U169 BSD-3-Clause Yes Details →
go1.11.2 — U169 BSD-3-Clause Yes Details →
go1.11.3 — U169 BSD-3-Clause Yes Details →
go1.11.4 — U169 BSD-3-Clause Yes Details →
go1.11.5 — U169 BSD-3-Clause Yes Details →
go1.11.6 — U169 BSD-3-Clause Yes Details →
go1.11.7 — U169 BSD-3-Clause Yes Details →
go1.11.8 — U169 BSD-3-Clause Yes Details →
go1.11.9 — U169 BSD-3-Clause Yes Details →
go1.11beta1 — U169 BSD-3-Clause Yes Details →
go1.11beta2 — U169 BSD-3-Clause Yes Details →
go1.11beta3 — U169 BSD-3-Clause Yes Details →
go1.11rc1 — U169 BSD-3-Clause Yes Details →
go1.11rc2 — U169 BSD-3-Clause Yes Details →
go1.12 — U169 BSD-3-Clause Yes Details →
go1.12.1 — U169 BSD-3-Clause Yes Details →
go1.12.10 — U169 BSD-3-Clause Yes Details →
go1.12.11 — U169 BSD-3-Clause Yes Details →
go1.12.12 — U169 BSD-3-Clause Yes Details →
go1.12.13 — U169 BSD-3-Clause Yes Details →
go1.12.14 — U169 BSD-3-Clause Yes Details →
go1.12.15 — U169 BSD-3-Clause Yes Details →
go1.12.16 — U169 BSD-3-Clause Yes Details →
go1.12.17 — U169 BSD-3-Clause Yes Details →
go1.12.2 — U169 BSD-3-Clause Yes Details →
go1.12.3 — U169 BSD-3-Clause Yes Details →
go1.12.4 — U169 BSD-3-Clause Yes Details →
go1.12.5 — U169 BSD-3-Clause Yes Details →
go1.12.6 — U169 BSD-3-Clause Yes Details →
go1.12.7 — U169 BSD-3-Clause Yes Details →
go1.12.8 — U169 BSD-3-Clause Yes Details →
go1.12.9 — U169 BSD-3-Clause Yes Details →
go1.12beta1 — U169 BSD-3-Clause Yes Details →
go1.12beta2 — U169 BSD-3-Clause Yes Details →
go1.12rc1 — U169 BSD-3-Clause Yes Details →
go1.13 — U169 BSD-3-Clause Yes Details →
go1.13.1 — U169 BSD-3-Clause Yes Details →
go1.13.10 — U169 BSD-3-Clause Yes Details →
go1.13.11 — U169 BSD-3-Clause Yes Details →
go1.13.12 — U169 BSD-3-Clause Yes Details →
go1.13.13 — U169 BSD-3-Clause Yes Details →
go1.13.14 — U169 BSD-3-Clause Yes Details →
go1.13.15 — U169 BSD-3-Clause Yes Details →
go1.13.2 — U169 BSD-3-Clause Yes Details →
go1.13.3 — U169 BSD-3-Clause Yes Details →
go1.13.4 — U169 BSD-3-Clause Yes Details →
go1.13.5 — U169 BSD-3-Clause Yes Details →
go1.13.6 — U169 BSD-3-Clause Yes Details →
go1.13.7 — U169 BSD-3-Clause Yes Details →
go1.13.8 — U169 BSD-3-Clause Yes Details →
go1.13.9 — U169 BSD-3-Clause Yes Details →
go1.13beta1 — U169 BSD-3-Clause Yes Details →
go1.13rc1 — U169 BSD-3-Clause Yes Details →
go1.13rc2 — U169 BSD-3-Clause Yes Details →
go1.14 — U169 BSD-3-Clause Yes Details →
go1.14.1 — U169 BSD-3-Clause Yes Details →
go1.14.10 — U169 BSD-3-Clause Yes Details →
go1.14.11 — U169 BSD-3-Clause Yes Details →
go1.14.12 — U169 BSD-3-Clause Yes Details →
go1.14.13 — U169 BSD-3-Clause Yes Details →
go1.14.14 — U169 BSD-3-Clause Yes Details →
go1.14.15 — U169 BSD-3-Clause Yes Details →
go1.14.2 — U169 BSD-3-Clause Yes Details →
go1.14.3 — U169 BSD-3-Clause Yes Details →
go1.14.4 — U169 BSD-3-Clause Yes Details →
go1.14.5 — U169 BSD-3-Clause Yes Details →
go1.14.6 — U169 BSD-3-Clause Yes Details →
go1.14.7 — U169 BSD-3-Clause Yes Details →
go1.14.8 — U169 BSD-3-Clause Yes Details →
go1.14.9 — U169 BSD-3-Clause Yes Details →
go1.14beta1 — U169 BSD-3-Clause Yes Details →
go1.14rc1 — U169 BSD-3-Clause Yes Details →
go1.15 — U169 BSD-3-Clause Yes Details →
go1.15.1 — U169 BSD-3-Clause Yes Details →
go1.15.10 — U169 BSD-3-Clause Yes Details →
go1.15.11 — U169 — Yes Details →
go1.15.12 — U169 — Yes Details →
go1.15.13 — U169 — Yes Details →
go1.15.14 — U169 — Yes Details →
go1.15.15 — U169 — Yes Details →
go1.15.2 — U169 — Yes Details →
go1.15.3 — U169 — Yes Details →
go1.15.4 — U169 — Yes Details →
go1.15.5 — U169 — Yes Details →
go1.15.6 — U169 — Yes Details →
go1.15.7 — U169 — Yes Details →
go1.15.8 — U169 — Yes Details →
go1.15.9 — U169 — Yes Details →
go1.15beta1 — U169 — Yes Details →
go1.15rc1 — U169 — Yes Details →
go1.15rc2 — U169 — Yes Details →
go1.16 — U169 — Yes Details →
go1.16.1 — U169 — Yes Details →
go1.16.10 — U169 — Yes Details →
go1.16.11 — U169 — Yes Details →

The newest 120 of 356 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2022 71
  • 2023 24
  • 2024 16
  • 2025 24
  • 2026 49

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

03 Vulnerabilities

Recorded vulnerabilities for stdlib

The 5 most severe of 186 vulnerabilities recorded for this package

Search all 186 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2019-9512: golang.org/x/net/http vulnerable to ping floods N/A unrated 1.11.13 01 Aug 2022
CVE-2026-111943: Go Standard Library - Distrust of Compromised Intermediate Certificates in crypto/x509 N/A unrated 1.26.10 21 Oct 2026
CVE-2025-4673: Go Standard Library net/http Sensitive Header Leak on Cross-Origin Redirects N/A unrated 1.23.10 11 Jun 2025
CVE-2025-22874: Go Standard Library - ExtKeyUsageAny Disables Policy Validation in crypto/x509 N/A unrated 1.24.4 11 Jun 2025
CVE-2025-0913: Go Standard Library - Inconsistent Handling of O_CREATE|O_EXCL on Unix and Windows N/A unrated 1.23.10 11 Jun 2025

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 stdlib

Is stdlib safe to use?

Vulert records 186 vulnerabilities for stdlib in Go: 0 critical, 0 high, 0 medium and 0 low, plus 186 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 stdlib's Vulert package health score?

Vulert scores stdlib 42/100, which reads as risky. 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 stdlib affected?

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

Which version of stdlib should I use?

go1.25.5 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 stdlib have?

186 vulnerabilities are recorded for stdlib in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 186 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 stdlib vulnerabilities disclosed?

61 vulnerabilities were recorded for stdlib in the last 12 months, and the oldest entry in this database dates to 14 Apr 2021. 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 stdlib 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 stdlib for upcoming vulnerabilities?

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