VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/docker/compose/v2: vulnerability history, versions and safety

github.com/docker/compose/v2 is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Oct 2025. 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 H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 27 Oct 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/docker/compose/v2 vulnerabilities

Vulert verdict on github.com/docker/compose/v2 v2.40.3 i

Updated on 23 Oct 2026

Action needed: v2.40.3 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 86/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 v2.40.3 — affected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 27 Oct 2025 i
  • Highest CVSS 8.9 i
  • With no published fix 0 i
  • Stars 38,421 i
  • OpenSSF scorecard 6/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/docker/compose/v2, 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
v2.40.3-0.20251112152424-f0dce1b977cd 12 Nov 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251112101728-45def51117a2 12 Nov 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251112101728-aff5c115d6ac 12 Nov 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251110151536-9de7e2a3882d 10 Nov 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251106152846-c37ede62dbb6 06 Nov 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251106092737-8137b2bce80e 06 Nov 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251106070259-67e39a41f2c7 06 Nov 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251105164311-0c596ed3cf95 05 Nov 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251104092514-fc2a7d13fa00 04 Nov 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251104091855-bff3d353052e 04 Nov 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251104091855-d70bb8cf5ef7 04 Nov 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251103075830-b80bb0586e42 03 Nov 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251103075830-d74274bc04fa 03 Nov 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251103070159-3658a063bbb5 03 Nov 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251031164438-74a4ccdd85f7 31 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.4-0.20251030202726-0d21922234ab 30 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3 30 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251030091250-3eb2934eb76c 30 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251030090829-c416ea70361a 30 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251029094718-fc74c7896308 29 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251029091130-394466683a06 29 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251029091130-a8933c91e79a 29 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251029091130-ae25d27e5a31 29 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251029091130-e5c8b68642bc 29 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251029091130-fd4f2f99cf32 29 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251028133950-bf50c99193a6 28 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251027175410-8274be8d087f 27 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251027151750-86e91e010df8 27 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251027151750-e1678c5c4366 27 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251027092418-5924387e89eb 27 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251024162421-7f668bd7fe75 24 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251024082159-3ce52883cbca 24 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251023161941-8619f5d72a2d 23 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251023100437-e59150baa800 23 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.3-0.20251022180932-6a90742ef29c 22 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.2 22 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.2-0.20251022173216-69bcb962bfb2 22 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.2-0.20251022141455-9b4fcce03478 22 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.1 17 Oct 2025 H1 Apache-2.0 Yes Details →
v2.40.0 03 Oct 2025 H1 Apache-2.0 Yes Details →
v2.39.5-0.20250926164507-8978c1027de7 26 Sep 2025 H1 Apache-2.0 Yes Details →
v2.39.4 19 Sep 2025 H1 Apache-2.0 Yes Details →
v2.39.3 08 Sep 2025 H1 Apache-2.0 Yes Details →
v2.39.3-0.20250908160700-385b3f5c9643 08 Sep 2025 H1 Apache-2.0 Yes Details →
v2.39.3-0.20250903124438-42d1e4c33309 03 Sep 2025 H1 Apache-2.0 Yes Details →
v2.39.3-0.20250902134614-6ca8663bda30 02 Sep 2025 H1 Apache-2.0 Yes Details →
v2.39.3-0.20250902052806-b33ecf65e866 02 Sep 2025 H1 Apache-2.0 Yes Details →
v2.39.3-0.20250829095042-04b8ac5fe4b9 29 Aug 2025 H1 Apache-2.0 Yes Details →
v2.39.3-0.20250827132517-1d69f4a68ca0 27 Aug 2025 H1 Apache-2.0 Yes Details →
v2.39.3-0.20250827070358-6078b4d99de5 27 Aug 2025 H1 Apache-2.0 Yes Details →
v2.39.3-0.20250825092225-51499f645b14 25 Aug 2025 H1 Apache-2.0 Yes Details →
v2.39.3-0.20250813073622-f266715dd031 13 Aug 2025 H1 Apache-2.0 Yes Details →
v2.39.2 08 Aug 2025 H1 Apache-2.0 Yes Details →
v2.39.2-0.20250806132709-f36ee00f71be 06 Aug 2025 H1 Apache-2.0 Yes Details →
v2.39.2-0.20250805115243-bf6d7bf47e0f 05 Aug 2025 H1 Apache-2.0 Yes Details →
v2.39.2-0.20250805080823-fc66da06dbaa 05 Aug 2025 H1 Apache-2.0 Yes Details →
v2.39.2-0.20250730093957-0dc9852c67b4 30 Jul 2025 H1 Apache-2.0 Yes Details →
v2.39.2-0.20250729122324-2c12ad19db50 29 Jul 2025 H1 Apache-2.0 Yes Details →
v2.39.2-0.20250728080703-52f04229c039 28 Jul 2025 H1 Apache-2.0 Yes Details →
v2.39.2-0.20250728072535-fe046915ebd8 28 Jul 2025 H1 Apache-2.0 Yes Details →
v2.39.2-0.20250727173640-adbd61e5d6c0 27 Jul 2025 H1 Apache-2.0 Yes Details →
v2.39.2-0.20250727131238-1946de598df6 27 Jul 2025 H1 Apache-2.0 Yes Details →
v2.39.1 24 Jul 2025 H1 Apache-2.0 Yes Details →
v2.39.0 24 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.3-0.20250723140128-95660c5e5a71 23 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.3-0.20250722100758-4d47da6dc2e4 22 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.3-0.20250721150741-8f91793fb532 21 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.3-0.20250721083150-3875e13fadec 21 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.3-0.20250718095956-5fc2b2a71cc4 18 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.3-0.20250717133538-362ab0733f4f 17 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.3-0.20250716153459-17ba6c7188fe 16 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.2-0.20250716152411-1c37f1abb688 16 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.2-0.20250716152411-485b6200ee00 16 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.2-0.20250716145126-8c17a35609da 16 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.3-0.20250716065912-9a1e589ce83e 16 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.3-0.20250711090808-cb959100188e 11 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.3-0.20250709080833-35efa97b7df6 09 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.2 08 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.2-0.20250708080634-69f1430a49ee 08 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.2-0.20250707083720-0e0ed91a3961 07 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.2-0.20250704104137-c626befee159 04 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.2-0.20250703093558-8faf1eb808ac 03 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.2-0.20250702094911-3b0601b6713d 02 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.2-0.20250702053100-b046a5ef7269 02 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.2-0.20250701125657-1570c6c07617 01 Jul 2025 H1 Apache-2.0 Yes Details →
v2.38.1 30 Jun 2025 H1 Apache-2.0 Yes Details →
v2.38.0 30 Jun 2025 H1 Apache-2.0 Yes Details →
v2.37.4-0.20250630172235-ee1b1e0a9359 30 Jun 2025 H1 Apache-2.0 Yes Details →
v2.37.4-0.20250627184449-3553aa26a660 27 Jun 2025 H1 Apache-2.0 Yes Details →
v2.37.4-0.20250626192633-c9ebfad78e1b 26 Jun 2025 H1 Apache-2.0 Yes Details →
v2.37.4-0.20250624151741-6514c680a50e 24 Jun 2025 H1 Apache-2.0 Yes Details →
v2.37.3 24 Jun 2025 H1 Apache-2.0 Yes Details →
v2.37.3-0.20250623190538-c97e40e2b8e5 23 Jun 2025 H1 Apache-2.0 Yes Details →
v2.37.3-0.20250622185035-22e23bd4dc19 22 Jun 2025 H1 Apache-2.0 Yes Details →
v2.37.3-0.20250622054438-2dde5faeb8c0 22 Jun 2025 H1 Apache-2.0 Yes Details →
v2.37.2 20 Jun 2025 H1 Apache-2.0 Yes Details →
v2.37.2-0.20250616091545-4f491ffa9869 16 Jun 2025 H1 Apache-2.0 Yes Details →
v2.37.2-0.20250613124316-9a5fa05ad6f8 13 Jun 2025 H1 Apache-2.0 Yes Details →
v2.37.1 12 Jun 2025 H1 Apache-2.0 Yes Details →
v2.37.1-0.20250612075220-f599a8cdd267 12 Jun 2025 H1 Apache-2.0 Yes Details →
v2.37.1-0.20250612074807-63b06f556330 12 Jun 2025 H1 — Yes Details →
v2.37.1-0.20250610073022-213c03f99afc 10 Jun 2025 H1 — Yes Details →
v2.37.1-0.20250607210749-ea48480d809a 07 Jun 2025 H1 — Yes Details →
v2.37.1-0.20250606142129-8151b5928875 06 Jun 2025 H1 — Yes Details →
v2.37.0 05 Jun 2025 H1 — Yes Details →
v2.36.3-0.20250605131232-92fafccfb297 05 Jun 2025 H1 — Yes Details →
v2.36.3-0.20250602165707-27e90a3fdfb2 02 Jun 2025 H1 — Yes Details →
v2.36.3-0.20250602090304-693b9ef07898 02 Jun 2025 H1 — Yes Details →
v2.36.3-0.20250531174032-60256a875c67 31 May 2025 H1 — Yes Details →
v2.36.3-0.20250528101216-45bd60c33a6c 28 May 2025 H1 — Yes Details →
v2.36.3-0.20250527141436-cf89fd1aa132 27 May 2025 H1 — Yes Details →
v2.36.3-0.20250526143745-bbb2b76a14de 26 May 2025 H1 — Yes Details →
v2.36.2 23 May 2025 H1 — Yes Details →
v2.36.2-0.20250522125853-a54814ff3921 22 May 2025 H1 — Yes Details →
v2.36.2-0.20250521135930-8a2cb90a3962 21 May 2025 H1 — Yes Details →
v2.36.2-0.20250520162105-7e198ee6a3b5 20 May 2025 H1 — Yes Details →
v2.36.2-0.20250520074758-4f6cc2a3307a 20 May 2025 H1 — Yes Details →
v2.36.1 19 May 2025 H1 — Yes Details →
v2.36.1-0.20250519103517-1f076a3781f2 19 May 2025 H1 — Yes Details →
v2.36.1-0.20250516154709-944e5e67a1dc 16 May 2025 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/docker/compose/v2

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-62725: Docker Compose Path Traversal Vulnerability in OCI Artifact Layer Annotations 8.9 high 2.40.2 27 Oct 2025

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/docker/compose/v2

Is github.com/docker/compose/v2 safe to use?

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

Vulert scores github.com/docker/compose/v2 86/100, which reads as healthy. 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/docker/compose/v2 affected?

Yes. v2.40.3, 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/docker/compose/v2 should I use?

v2.40.3 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/docker/compose/v2 have?

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

1 vulnerability was recorded for github.com/docker/compose/v2 in the last 12 months, and the oldest entry in this database dates to 27 Oct 2025. 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/docker/compose/v2 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/docker/compose/v2 for upcoming vulnerabilities?

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