Vulnerability Database · Go · Package report

github.com/distribution/distribution/v3: vulnerability history, versions and safety

github.com/distribution/distribution/v3 is a package in the Go ecosystem. Vulert records 3 vulnerabilities for it across 120 releases, from Apr 2026 to May 2026. 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 H2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 04 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/distribution/distribution/v3 v3.1.2 i

Updated on 23 Oct 2026

Action needed: v3.1.2 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 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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.1.2 — affected i
  • Vulnerabilities on record 3 over 1 year · 3 in the last year i
  • Latest disclosure 04 May 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 10,658 i
  • OpenSSF scorecard 6/10 i
  • Last release this month 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/distribution/distribution/v3, 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
v3.1.3-0.20261021151302-b9a474581122 21 Oct 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.3-0.20261020152936-cff0ff0c926e 20 Oct 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.3-0.20261018162538-952d81c67be4 18 Oct 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.3-0.20261016234607-042c3a9a51c3 16 Oct 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.3-0.20261014200017-f7d69d28c2e3 14 Oct 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.3-0.20261014175617-84baa4692de7 14 Oct 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.3-0.20261012032541-d7da5da1ce1d 12 Oct 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.3-0.20261008043625-bbf0a189dcae 08 Oct 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.3-0.20261007144839-fd9609dd58e2 07 Oct 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.3-0.20261005010548-8ceb7bbf72b3 05 Oct 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.3-0.20261001150954-f01dfc400e8f 01 Oct 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.3-0.20260930143706-1d71a5c78e86 30 Sep 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.3-0.20260929142503-e0904092e25f 29 Sep 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.3-0.20260928134607-905f26de4b02 28 Sep 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.3-0.20260926155004-923efdb825c7 26 Sep 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2 24 Sep 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260924013852-973fbf7e7559 24 Sep 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260923142518-960439b09f34 23 Sep 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260922171410-bc5876a2f2e5 22 Sep 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260922023526-a90fb174cac6 22 Sep 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260831195149-5b354e6fda61 31 Aug 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260818185522-0d6b721dc3ce 18 Aug 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260810190446-4f6036efc849 10 Aug 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260729173203-9f9289e23a13 29 Jul 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260723043206-652f98177439 23 Jul 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260721130836-8f91c26c8888 21 Jul 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260719031318-4d578730b82a 19 Jul 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260619145823-472c9d38c9fc 19 Jun 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260607162023-af1b4b4e9a9b 07 Jun 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260531193137-915084f4bc0c 31 May 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.2-0.20260501155316-7287385db888 01 May 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.0-20260501152851-9a8d98b67974 01 May 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.1 01 May 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.1-0.20260422180745-f3af4de047a0 22 Apr 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.1-0.20260420144728-1b5e226b6fe9 20 Apr 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.1-0.20260419000424-0f3e62793783 19 Apr 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.1-0.20260416211756-ca7d4de0ee71 16 Apr 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.1-0.20260412230955-6ae29aadd7b2 12 Apr 2026 H2 M1 Apache-2.0 Yes Details →
v3.1.0 06 Apr 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260406000850-078b0783f239 06 Apr 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260405203020-cc5d5fa4ba02 05 Apr 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260401153838-5cda72868f90 01 Apr 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260330152747-f215e513dee5 30 Mar 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260328004521-c7c980d7957d 28 Mar 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260325173719-d4164c1edb9c 25 Mar 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260323134530-ee3ba929f66d 23 Mar 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260320171903-ddf6218cd35a 20 Mar 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260319153433-d18d6cb923e6 19 Mar 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260317195752-bd2137921581 17 Mar 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260317180456-83dd82021c50 17 Mar 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260307210811-78a447df8e39 07 Mar 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260306162639-43a380e1e1ba 06 Mar 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260306072811-dcd6df96449f 06 Mar 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260305054946-90786adc267f 05 Mar 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260304214609-aa6ea57a949f 04 Mar 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260212230313-ab67ffa0bda3 12 Feb 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260212180632-3cf5a08615bf 12 Feb 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260212122251-f5d656e686d1 12 Feb 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260211212901-2cd77a0f4c3d 11 Feb 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260210203656-2a2c13c5c834 10 Feb 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260206210407-f2c2cf37bcfc 06 Feb 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260120145532-40594bd98e6d 20 Jan 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260109170818-4b93a062386b 09 Jan 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260108153442-814452f20b6e 08 Jan 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260107152328-f61aa941b374 07 Jan 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260106170321-47c426cf2e35 06 Jan 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20260105145041-2b2e2f475926 05 Jan 2026 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20251213085246-1796e65db96b 13 Dec 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20251121152623-10e4312e62ab 21 Nov 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20251121075957-abad58b9b165 21 Nov 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20251119233418-d1218cefd0ee 19 Nov 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20251114084823-c360968eb56b 14 Nov 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20251020154243-c287c7755b60 20 Oct 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20251019140929-4d613f771f45 19 Oct 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20251017190554-edde36cd9e68 17 Oct 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20251016072537-76fe6170526f 16 Oct 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20251015155939-8ce8219982a1 15 Oct 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20251013173834-283bd92b7846 13 Oct 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20251008061629-7d4be412e97c 08 Oct 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20251001065910-d595e0a17013 01 Oct 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250917055256-4ead5a108593 17 Sep 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250905081748-cf6a5ce3460a 05 Sep 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250903140609-979a07472ec4 03 Sep 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250813210925-412a8ae033e4 13 Aug 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250812150209-f2b08cd917f8 12 Aug 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250812054112-8c60ad709b0b 12 Aug 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250811222537-7f2dad4420da 11 Aug 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250811132741-7d74ee7186c9 11 Aug 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250811061453-c54bcb377096 11 Aug 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250811052807-f6e54e6189bf 11 Aug 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250808181124-f9fa20599273 08 Aug 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250722174515-e7b4fa06f2c8 22 Jul 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250710144449-c9760ebe959d 10 Jul 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250709182744-17dc6f9cdabf 09 Jul 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250602144614-da404778edd3 02 Jun 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250519143707-97495e53977f 19 May 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250504074319-dde1e49f2368 04 May 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250429132155-95647cba1d99 29 Apr 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250423152825-e827ce2772e0 23 Apr 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250417064513-e016d9595f53 17 Apr 2025 H2 M1 Apache-2.0 Yes Details →
v3.0.1-0.20250413141022-523791cb5f2b 13 Apr 2025 H2 M1 — Yes Details →
v3.0.1-0.20250409050957-e028a30ecd61 09 Apr 2025 H2 M1 — Yes Details →
v3.0.1-0.20250403190400-dbca4995c83c 03 Apr 2025 H2 M1 — Yes Details →
v3.0.0 02 Apr 2025 H2 M1 — Yes Details →
v3.0.0-rc.4.0.20250330191820-2e63da99776b 30 Mar 2025 H2 M1 — Yes Details →
v3.0.0-rc.4.0.20250330141722-fd14cf193339 30 Mar 2025 H2 M1 — Yes Details →
v3.0.0-rc.4.0.20250330034218-3a33ba12ad9a 30 Mar 2025 H2 M1 — Yes Details →
v3.0.0-rc.4.0.20250328153927-75f32197b6f1 28 Mar 2025 H2 M1 — Yes Details →
v3.0.0-rc.4.0.20250323163300-ef21149b4999 23 Mar 2025 H2 M1 — Yes Details →
v3.0.0-rc.4 22 Mar 2025 H2 M1 — Yes Details →
v3.0.0-rc.3.0.20250320200242-c6d55cb1a9bf 20 Mar 2025 H2 M1 — Yes Details →
v3.0.0-rc.3.0.20250320055153-c3a972297908 20 Mar 2025 H2 M1 — Yes Details →
v3.0.0-rc.3.0.20250318085443-65f455352d2f 18 Mar 2025 H2 M1 — Yes Details →
v3.0.0-rc.3.0.20250314172025-ebd20d3be77e 14 Mar 2025 H2 M1 — Yes Details →
v3.0.0-rc.3.0.20250311174809-2a47e444332e 11 Mar 2025 H2 M1 — Yes Details →
v3.0.0-rc.3.0.20250309200035-4974b855f660 09 Mar 2025 H2 M1 — Yes Details →
v3.0.0-rc.3.0.20250301154700-1b01625dae6a 01 Mar 2025 H2 M1 — Yes Details →
v3.0.0-rc.3.0.20250225144202-d9b0802d81b4 25 Feb 2025 H2 M1 — Yes Details →
v3.0.0-rc.3.0.20250225081621-27d490c4ab61 25 Feb 2025 H2 M1 — Yes Details →
v3.0.0-rc.3.0.20250224154125-9e96aec357bb 24 Feb 2025 H2 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/distribution/distribution/v3

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/distribution/distribution/v3

Is github.com/distribution/distribution/v3 safe to use?

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

Vulert scores github.com/distribution/distribution/v3 84/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/distribution/distribution/v3 affected?

Yes. v3.1.2, 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/distribution/distribution/v3 should I use?

v3.1.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/distribution/distribution/v3 have?

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

3 vulnerabilities were recorded for github.com/distribution/distribution/v3 in the last 12 months, and the oldest entry in this database dates to 06 Apr 2026. 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/distribution/distribution/v3 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/distribution/distribution/v3 for upcoming vulnerabilities?

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