Vulnerability Database · Go · Package report

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

github.com/containers/image is a package in the Go ecosystem. Vulert records 3 vulnerabilities for it across 120 releases, from Apr 2021 to May 2024. 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 H1 M1 U1
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/image v3.0.2+incompatible i

Updated on 23 Oct 2026

Action needed: v3.0.2+incompatible 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 64/100
  • Security Minor issues
  • Maintenance Slowing
  • 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 v3.0.2+incompatible — affected i
  • Vulnerabilities on record 3 over 3 years · 0 in the last year i
  • Latest disclosure 14 May 2024 i
  • Highest CVSS 8.3 i
  • With no published fix 0 i
  • Stars 968 i
  • OpenSSF scorecard 3/10 i
  • Last release 86 months ago i
  • Licence Apache-2.0 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/containers/image, 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-20200218102118-68801be89be5 18 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200218102112-42fb012c4cb1 18 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200218102106-d4d4a4506a5c 18 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200218102059-bf1af8220c13 18 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200207113519-a827ffa43977 07 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200207113513-7e282d923a5c 07 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200207113507-acf842191bbb 07 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200206121636-0af121f2fc64 06 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200206121632-2a65a14b919e 06 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200206121623-21c449b55b5c 06 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200206114714-2451afa3df5b 06 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200206114701-73bec4e5d6fd 06 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200206114336-b37c1bc3eefe 06 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v2.0.1-0.20200205134020-c150569d7ede+incompatible 05 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v2.0.1-0.20200205134015-fe049e98548f+incompatible 05 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v2.0.1-0.20200205134008-643e15862011+incompatible 05 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v2.0.1-0.20200205134002-3ee95509f441+incompatible 05 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200205131629-24693941df9d 05 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200205131618-b9383b565c19 05 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20200205131231-20055c722189 05 Feb 2020 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20191003205244-4a633785f49b 03 Oct 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20191003171942-7e017b7181f3 03 Oct 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20191003124408-100f3d7838c3 03 Oct 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20191002175354-b68372d54642 02 Oct 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20191001133803-cb8ac7927625 01 Oct 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20191001091021-a606bdc40114 01 Oct 2019 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20191001090940-b49a0b7eac5a 01 Oct 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20191001090940-b49a0b7eac5a 01 Oct 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20191001085711-df216d7cdc94 01 Oct 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20191001085621-e8c1452164ab 01 Oct 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190930152836-9632660d5b23 30 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190930152231-f77dc7dfe73e 30 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190930152119-e58240815d9a 30 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190930110316-aa9064da265d 30 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190929132850-9911c94ebb54 29 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190927194019-4ffc973d918b 27 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190927194019-73f3b7c5387e 27 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190927194019-7dbdc9548c4a 27 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190927194019-8d3e6883d7a6 27 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190927193948-0fcdae160706 27 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190927191425-618003c1a959 27 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190926181947-ddb11c057155 26 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190926174957-2adcf0784d89 26 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190926174930-b8ce1a20f13f 26 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190926153518-205ac4a6e053 26 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190926153415-97d8ea4052db 26 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190920130423-3e4758b5bcaf 20 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190920112514-0dca9fe07b98 20 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190918125936-dcdb9214e171 18 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190918110047-95443a4bc76d 18 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20190917185454-0d870c59cc81 17 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v2.0.1-0.20190917185454-0d870c59cc81+incompatible 17 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v2.0.1-0.20190917152334-fed456a3f840+incompatible 17 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v2.0.1-0.20190917144839-02cb1b432e16+incompatible 17 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190916193926-9bafe00f3912 16 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190916172822-d0338632bac7 16 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190916082455-b344f2f8a32c 16 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20190911175617-915c7e6d2070 11 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20190911173619-8c665c8c0bb5 11 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20190910152317-fe7bb4142701 10 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190909102020-69aa1e85460f 09 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190903174530-6617860c505c 03 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190903134823-3fd0ac2c7102 03 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190903133537-d9f643f354a4 03 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190903073329-c9e5b2704c07 03 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190902184242-335b34f9ac7d 02 Sep 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190823161458-713c8d43f997 23 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190823161458-713c8d43f997+incompatible 23 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190823161357-42160e7de679+incompatible 23 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190823161254-ccb81a3763f7+incompatible 23 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190823150736-7bc263abcbe1+incompatible 23 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190823150609-7a7310576eee+incompatible 23 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190823150545-d6b0c1a86c11+incompatible 23 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190823140714-d53a6543b985+incompatible 23 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190823132114-e7bbff750603+incompatible 23 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190822112454-78388d364638+incompatible 22 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190822083734-7bfa4acbc9b2+incompatible 22 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190821161828-0cc0e97405db 21 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190821161828-0cc0e97405db+incompatible 21 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190821133335-298142345838+incompatible 21 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v1.5.2-0.20190821113801-e003ccfc74de 21 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190821113801-e003ccfc74de+incompatible 21 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190813140229-9b055a514f21+incompatible 13 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190813140228-d0fb29f2d70d+incompatible 13 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190813140227-5b23c4b55a9e+incompatible 13 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190813140226-58c8793f8ead+incompatible 13 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190813140226-f89e6fbb0201+incompatible 13 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190807233145-7136ea743ea3+incompatible 07 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.3-0.20190807230338-8645d022d4f3+incompatible 07 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.2+incompatible 07 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.2-0.20190807212945-70a198608bb9+incompatible 07 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.2-0.20190807204054-24ef1410779c+incompatible 07 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.2-0.20190807122024-1f46e8a1009c+incompatible 07 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.2-0.20190806224033-fd116228f0b8+incompatible 06 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.2-0.20190805191858-67584976bd33+incompatible 05 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.2-0.20190805163343-19bee2c7ea3a+incompatible 05 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.1+incompatible 05 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.1-0.20190805163211-04d8b0f0e2ce+incompatible 05 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.1-0.20190805151228-a0ed68ea6d33+incompatible 05 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.1-0.20190805150929-64b622c1bc07+incompatible 05 Aug 2019 H1 M1 U1 Apache-2.0 Yes Details →
v3.0.1-0.20190805150830-3d148a9b232c+incompatible 05 Aug 2019 H1 M1 U1 — Yes Details →
v3.0.1-0.20190805123509-dd0113663d0d+incompatible 05 Aug 2019 H1 M1 U1 — Yes Details →
v3.0.1-0.20190802203331-d47f2a0045d5+incompatible 02 Aug 2019 H1 M1 U1 — Yes Details →
v3.0.1-0.20190802092231-ea74a03102f1+incompatible 02 Aug 2019 H1 M1 U1 — Yes Details →
v3.0.1-0.20190802091320-9d53febef082+incompatible 02 Aug 2019 H1 M1 U1 — Yes Details →
v3.0.0+incompatible 02 Aug 2019 H1 M1 U1 — Yes Details →
v2.0.2-0.20190802091223-d2897d758dd9+incompatible 02 Aug 2019 H1 M1 U1 — Yes Details →
v2.0.2-0.20190802084838-09d8ac074f03+incompatible 02 Aug 2019 H1 M1 U1 — Yes Details →
v2.0.2-0.20190802084709-e1aacd9a0af4+incompatible 02 Aug 2019 H1 M1 U1 — Yes Details →
v2.0.2-0.20190802081639-149456756dc0+incompatible 02 Aug 2019 H1 M1 U1 — Yes Details →
v2.0.2-0.20190802080134-634605d06e73+incompatible 02 Aug 2019 H1 M1 U1 — Yes Details →
v2.0.2-0.20190801194145-a3d69a4a8924+incompatible 01 Aug 2019 H1 M1 U1 — Yes Details →
v2.0.2-0.20190801131649-8ad47b442fea+incompatible 01 Aug 2019 H1 M1 U1 — Yes Details →
v2.0.2-0.20190731214921-4009bbea65df+incompatible 31 Jul 2019 H1 M1 U1 — Yes Details →
v2.0.2-0.20190731152212-78028ed33a83+incompatible 31 Jul 2019 H1 M1 U1 — Yes Details →
v2.0.2-0.20190731141954-11b916e4d459+incompatible 31 Jul 2019 H1 M1 U1 — Yes Details →
v2.0.2-0.20190726094551-6d69b602047a+incompatible 26 Jul 2019 H1 M1 U1 — Yes Details →
v2.0.2-0.20190725201841-c05af0514437+incompatible 25 Jul 2019 H1 M1 U1 — Yes Details →
v1.5.2-0.20190725091050-48acc3dcbb76 25 Jul 2019 H1 M1 U1 — Yes Details →
v2.0.2-0.20190725091050-48acc3dcbb76+incompatible 25 Jul 2019 H1 M1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 1
  • 2024 1

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/image

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/image

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

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

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

Yes. v3.0.2+incompatible, 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/image should I use?

v3.0.2+incompatible 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/image have?

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

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

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