VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/moby/moby: vulnerability history, versions and safety

github.com/moby/moby is a package in the Go ecosystem. Vulert records 14 vulnerabilities for it across 120 releases, from May 2022 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
14 vulnerabilities recorded H3 M7 U4
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 27 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/moby/moby vulnerabilities

Vulert verdict on github.com/moby/moby v28.5.2+incompatible i

Updated on 23 Oct 2026

Careful: v28.5.2+incompatible has 11 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v28.5.2+incompatible — affected i
  • Vulnerabilities on record 14 over 3 years · 1 in the last year i
  • Latest disclosure 27 Mar 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Stars 72,197 i
  • OpenSSF scorecard 7/10 i
  • Last release 11 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/moby/moby, 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
v25.0.19-0.20260930191552-13d41bca5f13+incompatible 30 Sep 2026 H3 M6 U2 Apache-2.0 No Details →
v25.0.18+incompatible 25 Aug 2026 H3 M6 U2 Apache-2.0 No Details →
v25.0.17+incompatible 14 Jul 2026 H3 M6 U2 Apache-2.0 No Details →
v25.0.17-0.20260525180023-6321e6370373+incompatible 25 May 2026 H3 M6 U2 Apache-2.0 No Details →
v25.0.16+incompatible 28 Apr 2026 H3 M6 U2 Apache-2.0 No Details →
v0.0.0-20260325154711-31a1689cb0a1 25 Mar 2026 H3 M6 U2 Apache-2.0 No Details →
v25.0.15-0.20260325154711-d2dbc0547253+incompatible 25 Mar 2026 H3 M6 U2 Apache-2.0 No Details →
v28.5.2-0.20260325154711-31a1689cb0a1+incompatible 25 Mar 2026 H3 M6 U2 Apache-2.0 No Details →
v28.5.3-0.20260325154711-31a1689cb0a1+incompatible 25 Mar 2026 H3 M6 U2 Apache-2.0 No Details →
v28.5.3-0.20260325120914-0afb41ce194c+incompatible 25 Mar 2026 H3 M6 U2 Apache-2.0 No Details →
v25.0.15+incompatible 31 Jan 2026 H3 M6 U2 Apache-2.0 No Details →
v25.0.15-0.20251126235524-f415784c1a8d+incompatible 26 Nov 2025 H3 M6 U2 Apache-2.0 No Details →
v28.5.2+incompatible 05 Nov 2025 H3 M6 U2 Apache-2.0 No Details →
v25.0.14+incompatible 09 Oct 2025 H3 M6 U2 Apache-2.0 No Details →
v28.5.1+incompatible 08 Oct 2025 H3 M6 U2 Apache-2.0 No Details →
v28.5.0+incompatible 01 Oct 2025 H3 M6 U2 Apache-2.0 No Details →
v28.5.0-rc.1.0.20251001152618-cd048300a487+incompatible 01 Oct 2025 H3 M6 U2 Apache-2.0 No Details →
v28.5.0-rc.1+incompatible 25 Sep 2025 H3 M6 U2 Apache-2.0 No Details →
v28.4.0+incompatible 03 Sep 2025 H3 M6 U2 Apache-2.0 No Details →
v28.4.0-rc.2.0.20250903202849-249d679a6baf+incompatible 03 Sep 2025 H3 M6 U2 Apache-2.0 No Details →
v28.4.0-rc.2+incompatible 02 Sep 2025 H3 M6 U2 Apache-2.0 No Details →
v28.4.0-rc.1+incompatible 29 Aug 2025 H3 M6 U2 Apache-2.0 No Details →
v25.0.13+incompatible 11 Aug 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250731183833-297ea75204cd+incompatible 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250731171308-53bd82885300+incompatible 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250731171308-a954a0f4a252+incompatible 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v0.0.0-20250731152656-4faedf2bec36 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250731152656-4faedf2bec36+incompatible 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250731134133-e55d294ea7bc+incompatible 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250731133841-8b68b977b13a+incompatible 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.3.4-0.20250731081225-501f2eab7ad0+incompatible 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v0.0.0-20250731053223-39030fdf942e 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250731053223-39030fdf942e+incompatible 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250731005739-5bbf3af9803a+incompatible 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250731005739-d58dc493fe8c+incompatible 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v0.0.0-20250731002424-0a5fb23b35df 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250731002424-0a5fb23b35df+incompatible 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250731001824-0564d7f0846f+incompatible 31 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730214656-494677f93f04+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730212212-f3ba0b2dc26c+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730212209-19edf5c53c04+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730205113-fdaccdb2331e+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v0.0.0-20250730165551-7bb2a152945e 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730165551-7bb2a152945e+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v0.0.0-20250730144150-263a21705b09 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730144150-263a21705b09+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730130059-94ac102e4b6b+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730122231-0d8ca8eefe94+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730122231-66862e14d16b+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730122231-d00ecdc479ca+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730122230-1da417980ce4+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730122230-5a144c40e2c3+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730122230-ebef4a44fd96+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730122230-f4127d76c565+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730122227-0515e1c99116+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v0.0.0-20250730122132-6453f9d5f4f8 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730122132-6453f9d5f4f8+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730122108-bda72b5c5750+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730122048-7c626bea7eb7+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730104802-9a52e474a37f+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730104146-02fcde0c184d+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730103445-e257027903cc+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250730101756-d7082848a630+incompatible 30 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v0.0.0-20250729125042-2574c2b2e917 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729125042-2574c2b2e917+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v0.0.0-20250729114952-1be59a838d36 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729114952-1be59a838d36+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729114747-7381c0da6e81+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v0.0.0-20250729113800-0e582c691ea2 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729113800-0e582c691ea2+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v0.0.0-20250729110540-12b761321b19 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729110540-12b761321b19+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729110439-6c7e2909c238+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729094857-5535e81a79f2+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729093623-03f44e6d141f+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729093623-28b822d5b33b+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729093623-450ac30e4a3d+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729093623-aa9de914cafe+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729093623-d94171bfaab7+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729093622-6f9e099fd364+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729093620-53a30852567a+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v0.0.0-20250729093552-8c7365e1ff47 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729093552-8c7365e1ff47+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729091732-1313b8caff26+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729091625-ae0a3d69186f+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729084735-bae46854c5ad+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729083926-46854ca5ab2c+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729082612-f1c65c1dd6ce+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729082209-f797ced96a1a+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729080744-e30d541da05f+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729080636-d80e16bb183f+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729075140-4c1ab68c6c6b+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729060519-03d7f47f31a0+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729060519-1dc53e8ec77b+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729060519-5bbb7182e7b0+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729050511-d7cfe9798410+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729024518-f86662130315+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729023013-df8d45c7c943+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729011839-ee24dcec3d5a+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v28.2.3-0.20250729002757-86190e73665d+incompatible 29 Jul 2025 H3 M6 U2 Apache-2.0 No Details →
v0.0.0-20250728205231-1e835a8cf58d 28 Jul 2025 H3 M6 U2 — No Details →
v28.2.3-0.20250728205231-1e835a8cf58d+incompatible 28 Jul 2025 H3 M6 U2 — No Details →
v28.2.3-0.20250728200439-d761d9d358b7+incompatible 28 Jul 2025 H3 M6 U2 — No Details →
v0.0.0-20250728192908-1e0531c8d55d 28 Jul 2025 H3 M6 U2 — No Details →
v28.2.3-0.20250728192908-1e0531c8d55d+incompatible 28 Jul 2025 H3 M6 U2 — No Details →
v0.0.0-20250728184435-0153bebebb2d 28 Jul 2025 H3 M6 U2 — No Details →
v28.2.3-0.20250728184435-0153bebebb2d+incompatible 28 Jul 2025 H3 M6 U2 — No Details →
v28.2.3-0.20250728184245-0075bafe0cab+incompatible 28 Jul 2025 H3 M6 U2 — No Details →
v28.2.3-0.20250728170200-17959aff2c24+incompatible 28 Jul 2025 H3 M6 U2 — No Details →
v28.2.3-0.20250728170017-c055c3e09856+incompatible 28 Jul 2025 H3 M6 U2 — No Details →
v28.2.3-0.20250728163922-76e2ca1d4178+incompatible 28 Jul 2025 H3 M6 U2 — No Details →
v28.2.3-0.20250728163215-f78d595c96ba+incompatible 28 Jul 2025 H3 M6 U2 — No Details →
v28.2.3-0.20250728163214-02867f94732f+incompatible 28 Jul 2025 H3 M6 U2 — No Details →
v28.2.3-0.20250728163214-5e567a385671+incompatible 28 Jul 2025 H3 M6 U2 — No Details →
v28.2.3-0.20250728163214-75bc4c52929a+incompatible 28 Jul 2025 H3 M6 U2 — No Details →
v0.0.0-20250728160505-a43c1eef183e 28 Jul 2025 H3 M6 U2 — No Details →
v28.3.3-0.20250728153907-c9c7964b7e97+incompatible 28 Jul 2025 H3 M6 U2 — No Details →
v0.0.0-20250728153048-1d6d8f390f26 28 Jul 2025 H3 M6 U2 — No Details →
v28.2.3-0.20250728153048-1d6d8f390f26+incompatible 28 Jul 2025 H3 M6 U2 — No Details →
v28.2.3-0.20250728115710-ec3e83a7b51d+incompatible 28 Jul 2025 H3 M6 U2 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2024 12
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/moby/moby

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-34040: Moby AuthZ Plugin Bypass Due to Oversized Request Bodies 8.8 high No fix published 27 Mar 2026
CVE-2024-36623: Moby Race Condition Vulnerability in Streamformatter Package 8.1 high 25.0.4 29 Nov 2024
CVE-2021-21284: Privilege Escalation in moby 6.8 medium 19.3.15 31 Jan 2024
CVE-2024-36621: Moby Race Condition Vulnerability in github.com/moby/moby 6.5 high 26.0.0 29 Nov 2024
CVE-2021-21285: Moby Docker Daemon Crash during Image Pull 6.5 medium 19.3.15 31 Jan 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/moby/moby

Is github.com/moby/moby safe to use?

Vulert records 14 vulnerabilities for github.com/moby/moby in Go: 0 critical, 3 high, 7 medium and 0 low, plus 4 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is github.com/moby/moby's Vulert package health score?

Vulert scores github.com/moby/moby 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/moby/moby affected?

Yes. v28.5.2+incompatible, the version you would install today, has 11 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/moby/moby should I use?

v28.5.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/moby/moby have?

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

1 vulnerability was recorded for github.com/moby/moby in the last 12 months, and the oldest entry in this database dates to 17 May 2022. 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/moby/moby 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/moby/moby for upcoming vulnerabilities?

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