VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

github.com/docker/buildx is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, first recorded in Mar 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded 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.

See all github.com/docker/buildx vulnerabilities

Vulert verdict on github.com/docker/buildx v0.38.1 i

Updated on 23 Oct 2026

Action needed: v0.38.1 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 89/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 v0.38.1 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 18 Mar 2025 i
  • Highest CVSS 4.1 i
  • With no published fix 0 i
  • Stars 4,536 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 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/buildx, 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.38.2-0.20261022104349-196b7d8da7aa 22 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.2-0.20261019095357-a9bcf45d2a7c 19 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.1-0.20261014143011-a44455e29f57 14 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.1-0.20261014131951-b9f19a4a8c03 14 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.1-0.20261012180742-c43f837d31f1 12 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.1-0.20261012152352-29207b1f8e19 12 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.1-0.20261012101319-d8d62f3c0740 12 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.1-0.20261009155218-c7748d0a0bdb 09 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.1-0.20261008113116-2b1e4d8995b3 08 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.0 07 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.1 07 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.0-rc2 06 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.0-rc1.0.20261005175814-0a20299836a4 05 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.0-rc1.0.20261001125402-63076c46bf08 01 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v0.38.0-rc1 30 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.2 30 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20260930142155-a69c132ded65 30 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20260929180416-188784897ae1 29 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20260926004733-809f4ef9892f 26 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20260921113833-44832b49688b 21 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20260918114713-3046cc7bafa7 18 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20260918065518-e8ab307a07de 18 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20260917022327-a371544fe5f5 17 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20260914122237-ddf35fcf46bd 14 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1 11 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20260911084153-bf5ccd4f3dc3 11 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20260910172959-393d6dffe703 10 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20260910171352-27a5fea92d47 10 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20260910094721-ef52678eb3dd 10 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20260908132757-364fbb16a1df 08 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.1-0.20260903093434-1b3aad3219b4 03 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.0 02 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.0-rc2 01 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.0-rc1.0.20260828120152-b6a8ce9bdd74 28 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.1-0.20260826225707-c07bc08336cf 26 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.37.0-rc1 26 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.1-0.20260826181936-544adadc4035 26 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.1-0.20260820141649-461836ba0fcb 20 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.1-0.20260814093946-5c83459f9798 14 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.1-0.20260811163858-fa6720d993b3 11 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.1-0.20260805161556-556e63ede01f 05 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.1-0.20260805103016-6b9f5324cab1 05 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.1-0.20260804151527-ef2dabd5c498 04 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.1 04 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.1-0.20260803141908-73b05c1446e4 03 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.1-0.20260730094835-595abeac8eef 30 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.0 29 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.0-rc2.0.20260728101706-41407679dcc8 28 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.0-rc2 27 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.0-rc1.0.20260723223150-05a1121b2930 23 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.36.0-rc1 22 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260720072111-a6718dc75383 20 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.35.0-rc2.0.20260720072111-a6718dc75383 20 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.35.0-rc2.0.20260717143819-8035347c81e6 17 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.35.0-rc2.0.20260711151413-aadce022ac11 11 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v0.35.0-rc2.0.20260629093757-5f67f9bcee6b 29 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260623063825-1d805d2ea211 23 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.35.0-rc2.0.20260623063825-1d805d2ea211 23 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260617193959-a319e5b15052 17 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.35.0 17 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.35.0-rc2.0.20260617193948-209f90c18c09 17 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.35.0-rc2.0.20260615175211-230fb952bba4 15 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260612120255-73e56595aae0 12 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.35.0-rc2 12 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.35.0-rc1 10 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.34.0-rc2.0.20260604134637-4fbc1e5f2c60 04 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.34.0-rc2.0.20260602141104-562b88ee69b6 02 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v0.34.0-rc2.0.20260522070712-3f3f6811ac2e 22 May 2026 M1 U1 Apache-2.0 Yes Details →
v0.34.1 19 May 2026 M1 U1 Apache-2.0 Yes Details →
v0.34.0-rc2.0.20260519152144-629301cffbd4 19 May 2026 M1 U1 Apache-2.0 Yes Details →
v0.34.0-rc2.0.20260514180312-4361a61408da 14 May 2026 M1 U1 Apache-2.0 Yes Details →
v0.34.0 13 May 2026 M1 U1 Apache-2.0 Yes Details →
v0.34.0-rc2.0.20260513133720-3808fba7df5f 13 May 2026 M1 U1 Apache-2.0 Yes Details →
v0.34.0-rc2 11 May 2026 M1 U1 Apache-2.0 Yes Details →
v0.34.0-rc1 06 May 2026 M1 U1 Apache-2.0 Yes Details →
v0.33.1-0.20260427121509-f1b60d200390 27 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.33.1-0.20260424162110-f9c1a462501b 24 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.33.1-0.20260407150101-d61060eb9528 07 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.33.1-0.20260403183647-b180175396a5 03 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v0.33.0 31 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.33.0-rc1.0.20260327134043-ce058179ed17 27 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.33.0-rc1 25 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.32.0-rc2.0.20260309234438-a5f49f0c1767 09 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.32.0-rc2.0.20260306105723-bb481888f985 06 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.32.0-rc2.0.20260304175804-d315c086c391 04 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.32.0 03 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.32.1 03 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.32.0-rc2.0.20260303203847-08998a7e901a 03 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v0.32.0-rc2 27 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v0.32.0-rc1 24 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v0.31.1-0.20260223171543-5830f90bebcb 23 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v0.31.1-0.20260210195930-9d803b0d8737 10 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v0.31.1-0.20260128211447-d88bf660cea1 28 Jan 2026 M1 U1 Apache-2.0 Yes Details →
v0.31.1 28 Jan 2026 M1 U1 Apache-2.0 Yes Details →
v0.31.1-0.20260127115814-841017f66541 27 Jan 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20260123175020-8f71a4805e66 23 Jan 2026 M1 U1 Apache-2.0 Yes Details →
v0.31.0 21 Jan 2026 M1 U1 Apache-2.0 Yes Details →
v0.31.0-rc2 16 Jan 2026 M1 U1 Apache-2.0 Yes Details →
v0.31.0-rc1 14 Jan 2026 M1 U1 Apache-2.0 Yes Details →
v0.30.0-rc2.0.20260114170342-d0e9e8cab5ad 14 Jan 2026 M1 U1 Apache-2.0 Yes Details →
v0.30.0-rc2.0.20260107194408-752e0b2227b3 07 Jan 2026 M1 U1 — Yes Details →
v0.30.0-rc2.0.20260106190608-1fa2ad4fa421 06 Jan 2026 M1 U1 — Yes Details →
v0.30.0-rc2.0.20251217174134-2bcb098cbb93 17 Dec 2025 M1 U1 — Yes Details →
v0.30.0-rc2.0.20251215144936-150cc839f252 15 Dec 2025 M1 U1 — Yes Details →
v0.30.0-rc2.0.20251213000735-590adceb63c8 13 Dec 2025 M1 U1 — Yes Details →
v0.30.0-rc2.0.20251211173855-d56379477ee2 11 Dec 2025 M1 U1 — Yes Details →
v0.30.0-rc2.0.20251205082252-22e7bf645512 05 Dec 2025 M1 U1 — Yes Details →
v0.30.0-rc2.0.20251203170011-4eb80cafb98a 03 Dec 2025 M1 U1 — Yes Details →
v0.30.0-rc2.0.20251203003331-f72bd30200ba 03 Dec 2025 M1 U1 — Yes Details →
v0.30.0-rc2.0.20251128003604-c6ec16cbc0e7 28 Nov 2025 M1 U1 — Yes Details →
v0.30.0-rc2.0.20251125173722-f1a0fc5d6379 25 Nov 2025 M1 U1 — Yes Details →
v0.30.1 17 Nov 2025 M1 U1 — Yes Details →
v0.30.0-rc2.0.20251117163012-3c9cd19e549e 17 Nov 2025 M1 U1 — Yes Details →
v0.30.0-rc2.0.20251115102242-823e824baf2e 15 Nov 2025 M1 U1 — Yes Details →
v0.30.0-rc2.0.20251113140532-45731b890203 13 Nov 2025 M1 U1 — Yes Details →
v0.0.0-20251112191151-124418cd66f0 12 Nov 2025 M1 U1 — Yes Details →
v0.30.0 12 Nov 2025 M1 U1 — Yes Details →
v0.30.0-rc2.0.20251112190344-a2cf0edfb404 12 Nov 2025 M1 U1 — Yes Details →
v0.30.0-rc2.0.20251112003002-18dc2e088af0 12 Nov 2025 M1 U1 — Yes Details →
v0.30.0-rc2 11 Nov 2025 M1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/docker/buildx

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-0495: GitHub Buildx Credential Leakage via Telemetry Endpoint 4.1 medium 0.21.3 17 Mar 2025
Credential Leakage Vulnerability in Docker Buildx Package N/A unrated 0.21.3 18 Mar 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/buildx

Is github.com/docker/buildx safe to use?

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

Vulert scores github.com/docker/buildx 89/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/buildx affected?

Yes. v0.38.1, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/docker/buildx should I use?

v0.38.1 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/buildx have?

2 vulnerabilities are recorded for github.com/docker/buildx in the Go ecosystem: 0 critical, 0 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/docker/buildx vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/docker/buildx in the last 12 months, and the oldest entry in this database dates to 17 Mar 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/buildx 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/buildx for upcoming vulnerabilities?

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