VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

github.com/containers/image/v5 is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in 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
1 vulnerabilities recorded 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.

See all github.com/containers/image/v5 vulnerabilities

Vulert verdict on github.com/containers/image/v5 v5.36.2 i

Updated on 23 Oct 2026

Action needed: v5.36.2 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 74/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 v5.36.2 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 20 May 2024 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 968 i
  • OpenSSF scorecard 3/10 i
  • Last release 13 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/v5, 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
v5.36.2 02 Sep 2025 U1 Apache-2.0 Yes Details →
v5.36.2-0.20250829160924-df7e80d2d198 29 Aug 2025 U1 Apache-2.0 Yes Details →
v5.36.2-0.20250826081346-ce4eca79f2d5 26 Aug 2025 U1 Apache-2.0 Yes Details →
v5.36.2-0.20250825172340-9b99818eb1db 25 Aug 2025 U1 Apache-2.0 Yes Details →
v5.36.2-0.20250820182922-19834a073bd6 20 Aug 2025 U1 Apache-2.0 Yes Details →
v5.36.2-0.20250819202644-702b97b5b44f 19 Aug 2025 U1 Apache-2.0 Yes Details →
v5.36.2-0.20250818183122-6a232fec5faf 18 Aug 2025 U1 Apache-2.0 Yes Details →
v5.36.2-0.20250812171152-52ee4dff559a 12 Aug 2025 U1 Apache-2.0 Yes Details →
v5.36.2-0.20250808142002-898f38590573 08 Aug 2025 U1 Apache-2.0 Yes Details →
v5.36.2-0.20250807195248-f8cef395fcde 07 Aug 2025 U1 Apache-2.0 Yes Details →
v5.36.1-0.20250805131829-2ba51d7e51ff 05 Aug 2025 U1 Apache-2.0 Yes Details →
v5.36.1-0.20250804214209-bba18c6a16cf 04 Aug 2025 U1 Apache-2.0 Yes Details →
v5.36.1 04 Aug 2025 U1 Apache-2.0 Yes Details →
v5.36.1-0.20250803054242-ae0757d3832a 03 Aug 2025 U1 Apache-2.0 Yes Details →
v5.36.1-0.20250802124957-b5ddf17d6f6b 02 Aug 2025 U1 Apache-2.0 Yes Details →
v5.36.1-0.20250728122815-569e40f9cb43 28 Jul 2025 U1 Apache-2.0 Yes Details →
v5.36.1-0.20250725175818-dcf72c931103 25 Jul 2025 U1 Apache-2.0 Yes Details →
v5.36.1-0.20250724140928-c54cb9c2c7cd 24 Jul 2025 U1 Apache-2.0 Yes Details →
v5.36.1-0.20250724133842-4b4473bb78d5 24 Jul 2025 U1 Apache-2.0 Yes Details →
v5.36.1-0.20250722100635-021aa7fe002a 22 Jul 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250715134332-5424d4659d7f 15 Jul 2025 U1 Apache-2.0 Yes Details →
v5.36.1-0.20250715134332-5424d4659d7f 15 Jul 2025 U1 Apache-2.0 Yes Details →
v5.36.0 14 Jul 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250714114753-9e95082de671 14 Jul 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250711125451-ccfad4e90ac4 11 Jul 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250710173754-d9a97d88aba7 10 Jul 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250709212130-d4dac818368e 09 Jul 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250707180819-778317a88563 07 Jul 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250704160045-8b4bc5098641 04 Jul 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250703163716-35325479c8f4 03 Jul 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250701145651-e3533743f666 01 Jul 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250630154900-a7d5329d9fa9 30 Jun 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250627164940-d1b934afaf03 27 Jun 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250627132650-84bfe041dbcc 27 Jun 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250625184553-c0fdf1637f3d 25 Jun 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250624174609-4f38ae207c2b 24 Jun 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250618182927-539b1c575043 18 Jun 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250611113617-c48f2e1f516e 11 Jun 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250606001011-9822b6ffa5c1 06 Jun 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250603145948-347a6e7283ef 03 Jun 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250602173359-cdce0b6aa871 02 Jun 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250531132325-6cbf3391241e 31 May 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250530200708-a89b1a77e672 30 May 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250530193806-2cdec77a8f91 30 May 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250529211017-ac57ff0c0040 29 May 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250526152843-c64593da00e4 26 May 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250514190820-3152ce9a4079 14 May 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250513181616-f2c6db9d4b45 13 May 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250512193856-5654350c1d4f 12 May 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250509124647-0e1556231852 09 May 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250506135150-fea2fe0d7a5f 06 May 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250505184014-baa65265b333 05 May 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250430102625-c48e2cabb758 30 Apr 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250428194407-3d418b5b5b59 28 Apr 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250422160725-25d70d7f1686 22 Apr 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250417204714-e2534e0da6ec 17 Apr 2025 U1 Apache-2.0 Yes Details →
v5.35.1-0.20250416180755-1bc3b14001fa 16 Apr 2025 U1 Apache-2.0 Yes Details →
v5.35.0 16 Apr 2025 U1 Apache-2.0 Yes Details →
v5.34.4-0.20250414103325-4279b172c41a 14 Apr 2025 U1 Apache-2.0 Yes Details →
v5.34.4-0.20250411224952-12c8495ca2fc 11 Apr 2025 U1 Apache-2.0 Yes Details →
v5.34.4-0.20250411164019-9b83c49abf09 11 Apr 2025 U1 Apache-2.0 Yes Details →
v5.34.4-0.20250408215611-6116c415e635 08 Apr 2025 U1 Apache-2.0 Yes Details →
v5.34.4-0.20250407202306-b4cabfdceb7a 07 Apr 2025 U1 Apache-2.0 Yes Details →
v5.34.4-0.20250404171426-f1abed77f4e9 04 Apr 2025 U1 Apache-2.0 Yes Details →
v5.34.4-0.20250402185326-4a3ed8c24dc3 02 Apr 2025 U1 Apache-2.0 Yes Details →
v5.34.4-0.20250401180700-7dd90864fc78 01 Apr 2025 U1 Apache-2.0 Yes Details →
v5.34.4-0.20250327193514-d3b241257363 27 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3 27 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250326211539-08d14a7ee24b 26 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250326191717-cb71b8dc79cc 26 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250325230645-987e2423c426 25 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250324182957-22415d4f7ea9 24 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250324170122-cfeba44147fc 24 Mar 2025 U1 Apache-2.0 Yes Details →
v5.32.3-0.20250321090242-db55860a7cf9 21 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250319215244-62f5380c196c 19 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250318194203-98c9f1b44eb2 18 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250317181540-7600f7fd56d9 17 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250314175833-afbcf2ea4659 14 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250314011931-36a971d8ff51 14 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250313215115-1fe90d955754 13 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250313191818-7af98c7178ef 13 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250313174407-4e32a672d24f 13 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250313163447-2c3e492ad6ab 13 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250312185629-4c5a86a9eb09 12 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250311194052-d84dbab374e7 11 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250311190441-99996a1a92ee 11 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.3-0.20250311170105-dcc9a83d6cbc 11 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.2 07 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.2-0.20250306154130-12497efe55ac 06 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.2-0.20250305212659-02c8d65a46de 05 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.2-0.20250304214348-1b336cac2494 04 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.2-0.20250304184223-c43e62eed23a 04 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.1-0.20250304003625-9260bafe58c6 04 Mar 2025 U1 Apache-2.0 Yes Details →
v5.34.1-0.20250228192257-16ec61f64072 28 Feb 2025 U1 Apache-2.0 Yes Details →
v5.34.1 28 Feb 2025 U1 Apache-2.0 Yes Details →
v5.34.1-0.20250228150120-1455d0f6a38b 28 Feb 2025 U1 Apache-2.0 Yes Details →
v5.34.1-0.20250228060909-57e8568849c6 28 Feb 2025 U1 Apache-2.0 Yes Details →
v5.34.1-0.20250227215338-e4a0c90bdc94 27 Feb 2025 U1 Apache-2.0 Yes Details →
v5.34.1-0.20250227212607-3961b828095e 27 Feb 2025 U1 Apache-2.0 Yes Details →
v5.34.1-0.20250220214519-041279524132 20 Feb 2025 U1 Apache-2.0 Yes Details →
v5.34.1-0.20250220175706-1c9baac64aa9 20 Feb 2025 U1 — Yes Details →
v5.34.1-0.20250220160145-1028e86e3418 20 Feb 2025 U1 — Yes Details →
v5.34.1-0.20250219183841-45cc0ab45c89 19 Feb 2025 U1 — Yes Details →
v5.34.1-0.20250217182618-c30cc7a54783 17 Feb 2025 U1 — Yes Details →
v5.34.1-0.20250213004352-aa915b75e867 13 Feb 2025 U1 — Yes Details →
v5.34.1-0.20250212202842-7d81a8ff7169 12 Feb 2025 U1 — Yes Details →
v5.34.1-0.20250212155221-e7feaf5bb0bb 12 Feb 2025 U1 — Yes Details →
v5.34.1-0.20250208023425-8d501c721b6a 08 Feb 2025 U1 — Yes Details →
v5.34.1-0.20250203223158-bdbd79ec2f9d 03 Feb 2025 U1 — Yes Details →
v5.34.1-0.20250131200606-7bcadcb156fa 31 Jan 2025 U1 — Yes Details →
v5.34.1-0.20250131134740-46ec7937d73b 31 Jan 2025 U1 — Yes Details →
v5.34.0 30 Jan 2025 U1 — Yes Details →
v5.33.2-0.20250127205030-7f0e59d15a6d 27 Jan 2025 U1 — Yes Details →
v5.33.2-0.20250122233652-b5c6aff95ca7 22 Jan 2025 U1 — Yes Details →
v5.33.2-0.20250122201336-16f7e1e0e1fd 22 Jan 2025 U1 — Yes Details →
v5.33.2-0.20250122193521-b10f5bdaa76f 22 Jan 2025 U1 — Yes Details →
v5.33.1-0.20250121231649-a45ebe065b9e 21 Jan 2025 U1 — Yes Details →
v5.33.1-0.20250121214714-77582bba6791 21 Jan 2025 U1 — Yes Details →
v5.33.1-0.20250121211332-2e79eabb4383 21 Jan 2025 U1 — Yes Details →
v5.33.1-0.20250121211315-ecd79c154c01 21 Jan 2025 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/containers/image/v5

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-3727: Unexpected Authenticated Registry Accesses in github.com/containers/image/v5 N/A unrated 5.29.3 20 May 2024

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

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

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

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

Yes. v5.36.2, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

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

v5.36.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/containers/image/v5 have?

1 vulnerability is recorded for github.com/containers/image/v5 in the Go ecosystem: 0 critical, 0 high, 0 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/v5 vulnerabilities disclosed?

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

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