Vulnerability Database · Go · Package report

github.com/containers/storage: vulnerability history, versions and safety

github.com/containers/storage is a package in the Go ecosystem. Vulert records 3 vulnerabilities for it across 120 releases, from May 2021 to Jul 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M1 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.

Vulert verdict on github.com/containers/storage v1.59.1 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

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.59.1 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 28 Jul 2021 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Stars 644 i
  • OpenSSF scorecard 4/10 i
  • Last release 14 months ago i
  • Licence Apache-2.0 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 github.com/containers/storage, 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.51.3 08 May 2026 M1 U2 Apache-2.0 Yes Details →
v1.59.2-0.20251113164137-606f1e4a4b26 13 Nov 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20251113163822-49977ac2f9e4 13 Nov 2025 M1 U2 Apache-2.0 Yes Details →
v1.56.1-0.20251113162132-a67c53ed17ca 13 Nov 2025 M1 U2 Apache-2.0 Yes Details →
v1.55.1-0.20251113162127-957e4b051fdf 13 Nov 2025 M1 U2 Apache-2.0 Yes Details →
v1.51.1-0.20251113162119-8c625df4a3ad 13 Nov 2025 M1 U2 Apache-2.0 Yes Details →
v1.51.1-0.20251113162101-4f06d0a37c1a 13 Nov 2025 M1 U2 Apache-2.0 Yes Details →
v1.49.1-0.20251113162046-ea4b4f0e75b8 13 Nov 2025 M1 U2 Apache-2.0 Yes Details →
v1.46.2-0.20251113162042-58ebf123b0cb 13 Nov 2025 M1 U2 Apache-2.0 Yes Details →
v1.46.2-0.20251113162038-fdb733e070d3 13 Nov 2025 M1 U2 Apache-2.0 Yes Details →
v1.46.2-0.20251113162035-6687bf16ffa6 13 Nov 2025 M1 U2 Apache-2.0 Yes Details →
v0.0.0-20250829161424-83cf57466529 29 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v1.59.2-0.20250829161424-83cf57466529 29 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v0.0.0-20250826082133-4d99797961df 26 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v1.59.2-0.20250826082133-4d99797961df 26 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v0.0.0-20250820181736-3f7c116059ca 20 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v1.59.2-0.20250820181736-3f7c116059ca 20 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v0.0.0-20250820174943-fb05ffb3206e 20 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v0.0.0-20250820165626-6b69d0d8855e 20 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v0.0.0-20250820122535-1dc24bce0a4b 20 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v1.59.2-0.20250820122535-1dc24bce0a4b 20 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v0.0.0-20250804212020-bf9084b26e02 04 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v1.59.1-0.20250804212020-bf9084b26e02 04 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v0.0.0-20250801182600-41839ee723fe 01 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v1.59.1 01 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v1.59.1-0.20250801154125-afc0ad64a7bb 01 Aug 2025 M1 U2 Apache-2.0 Yes Details →
v1.59.1-0.20250728151553-54892edf2e03 28 Jul 2025 M1 U2 Apache-2.0 Yes Details →
v1.59.1-0.20250728144808-8aad48ae2da3 28 Jul 2025 M1 U2 Apache-2.0 Yes Details →
v0.0.0-20250718022333-f555b9f2ddae 18 Jul 2025 M1 U2 Apache-2.0 Yes Details →
v1.59.1-0.20250718022333-f555b9f2ddae 18 Jul 2025 M1 U2 Apache-2.0 Yes Details →
v0.0.0-20250716144554-82a4546eb633 16 Jul 2025 M1 U2 Apache-2.0 Yes Details →
v1.59.1-0.20250714160143-0001aac2fbb3 14 Jul 2025 M1 U2 Apache-2.0 Yes Details →
v1.59.1-0.20250714152602-d1a23cdaba22 14 Jul 2025 M1 U2 Apache-2.0 Yes Details →
v0.0.0-20250714152527-51223aa059d7 14 Jul 2025 M1 U2 Apache-2.0 Yes Details →
v1.59.0 14 Jul 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250711145627-2b18ddcfafca 11 Jul 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250710201318-092254c04b62 10 Jul 2025 M1 U2 Apache-2.0 Yes Details →
v0.0.0-20250701152554-3aa733962202 01 Jul 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250701152554-3aa733962202 01 Jul 2025 M1 U2 Apache-2.0 Yes Details →
v0.0.0-20250701145805-3283983aec5c 01 Jul 2025 M1 U2 Apache-2.0 Yes Details →
v0.0.0-20250625164029-83650abfa8de 25 Jun 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250625164029-83650abfa8de 25 Jun 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250609114924-e1679c1222b3 09 Jun 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250609111722-1a704f7c6ea4 09 Jun 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250609093421-fe6561f61b3f 09 Jun 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250606204514-07c0c32c6208 06 Jun 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250515004000-78f4258b2bd9 15 May 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250507171116-36d562d33cf2 07 May 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250506192419-9ef75c10ed7a 06 May 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250506073204-9a881eeda35d 06 May 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250429190216-5ffb1d9d484e 29 Apr 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250429131912-ff9e524dc0c0 29 Apr 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250429102657-f5bdfdc07e19 29 Apr 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250423071752-eda48a7c38de 23 Apr 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250421124559-29f052f570bb 21 Apr 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250420161953-cdf5683faad6 20 Apr 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250415214331-6daf2ab1a66c 15 Apr 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.1-0.20250415214331-6daf2ab1a66c 15 Apr 2025 M1 U2 Apache-2.0 Yes Details →
v1.58.0 15 Apr 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250410091806-f01643a25302 10 Apr 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250408180038-b1d1b4586ecb 08 Apr 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250404205605-2312459c2644 04 Apr 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250401220008-f1c4bdf1d7c1 01 Apr 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250331162343-3fc5c230951d 31 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.55.1-0.20250328180621-028e88d2378c 28 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250328173230-c800027dd3df 28 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250327200749-7595f1842df0 27 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250326205630-e9b6c1093d29 26 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250325222852-4d1ae4a7983d 25 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250321202609-92bf4f2cbff6 21 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250318184648-bf8bcfedf1a6 18 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250317173258-9d0aca01ca19 17 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250314043721-13708c610642 14 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250312210131-2b84c2a846e6 12 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.3-0.20250310120440-ab85543c3c6a 10 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.2 06 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.2-0.20250306151931-b76b4b728478 06 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.2-0.20250305225826-ffc4407927b2 05 Mar 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.2-0.20250228100055-700b765b2111 28 Feb 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.2-0.20250220203011-3a013da40ef1 20 Feb 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.2-0.20250214174508-b6f6fb27264f 14 Feb 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.2-0.20250214093010-141b059b3168 14 Feb 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.2-0.20250211190637-7aa96daee0a3 11 Feb 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.1-0.20250210200321-13a758ff4ecb 10 Feb 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.1-0.20250204215511-5a2ca6ab27aa 04 Feb 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.1-0.20250203212212-bdde868c8f8a 03 Feb 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.1-0.20250131200947-ac7a05f7a99b 31 Jan 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.1-0.20250130214839-caf1ed408ec7 30 Jan 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.1 30 Jan 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.1-0.20250130171750-009737bdce0f 30 Jan 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.1-0.20250130171750-0dbf0feab951 30 Jan 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.1-0.20250130171750-9c42f91cd8dd 30 Jan 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.1-0.20250130130839-c2338384052c 30 Jan 2025 M1 U2 Apache-2.0 Yes Details →
v1.57.0 29 Jan 2025 M1 U2 Apache-2.0 Yes Details →
v1.56.2-0.20250127203306-053429cff57d 27 Jan 2025 M1 U2 Apache-2.0 Yes Details →
v1.56.1-0.20250123153752-b78c0cb4aa19 23 Jan 2025 M1 U2 Apache-2.0 Yes Details →
v1.55.1-0.20250123153357-a030a4472622 23 Jan 2025 M1 U2 Apache-2.0 Yes Details →
v1.51.1-0.20250123153027-e1bc50e6f958 23 Jan 2025 M1 U2 Apache-2.0 Yes Details →
v1.51.1-0.20250123152629-2d261ce40d92 23 Jan 2025 M1 U2 Apache-2.0 Yes Details →
v1.49.1-0.20250123135526-840468eb636c 23 Jan 2025 M1 U2 Apache-2.0 Yes Details →
v1.46.2-0.20250123134856-488507d8ac3d 23 Jan 2025 M1 U2 — Yes Details →
v1.46.2-0.20250123134623-3e6a23c6e0ea 23 Jan 2025 M1 U2 — Yes Details →
v1.56.2-0.20250123125217-80d3c0e77d29 23 Jan 2025 M1 U2 — Yes Details →
v1.56.2-0.20250122163553-1ff5f1c0068c 22 Jan 2025 M1 U2 — Yes Details →
v1.56.2-0.20250121150636-c2cdd500e4ef 21 Jan 2025 M1 U2 — Yes Details →
v1.46.2-0.20250117062443-5b73e51245af 17 Jan 2025 M1 U2 — Yes Details →
v1.46.2-0.20250117062051-730266634e11 17 Jan 2025 M1 U2 — Yes Details →
v1.46.2-0.20250117060752-72feeff89e43 17 Jan 2025 M1 U2 — Yes Details →
v1.56.2-0.20250115211129-aef3f600e98a 15 Jan 2025 M1 U2 — Yes Details →
v1.49.1-0.20250115015204-d9d9961e8fa1 15 Jan 2025 M1 U2 — Yes Details →
v1.56.1-0.20250114220529-0d4a8d2aaf29 14 Jan 2025 M1 U2 — Yes Details →
v1.56.1 14 Jan 2025 M1 U2 — Yes Details →
v1.56.1-0.20250113164809-08893fe4a60b 13 Jan 2025 M1 U2 — Yes Details →
v1.56.1-0.20250109200001-896fea9f38ed 09 Jan 2025 M1 U2 — Yes Details →
v1.56.1-0.20250109030507-3d75bd3f5064 09 Jan 2025 M1 U2 — Yes Details →
v1.56.1-0.20250107155609-9119f3691868 07 Jan 2025 M1 U2 — Yes Details →
v1.56.1-0.20250107082106-b87bac8fb133 07 Jan 2025 M1 U2 — Yes Details →
v1.56.1-0.20250106221731-22921780d2dd 06 Jan 2025 M1 U2 — Yes Details →
v1.56.1-0.20250102204143-48e12ae2d80f 02 Jan 2025 M1 U2 — Yes Details →
v1.56.1-0.20241219143414-8a1de75726e3 19 Dec 2024 M1 U2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 3

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/containers/storage

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →

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/containers/storage

Is github.com/containers/storage safe to use?

Vulert records 3 vulnerabilities for github.com/containers/storage in Go: 0 critical, 0 high, 1 medium and 0 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/containers/storage's Vulert package health score?

Vulert scores github.com/containers/storage 76/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/containers/storage affected?

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

Which version of github.com/containers/storage should I use?

v1.59.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/containers/storage have?

3 vulnerabilities are recorded for github.com/containers/storage in the Go ecosystem: 0 critical, 0 high, 1 medium and 0 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/containers/storage vulnerabilities disclosed?

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

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