Vulnerability Database · Go · Package report

github.com/go-git/go-billy/v5: vulnerability history, versions and safety

github.com/go-git/go-billy/v5 is a package in the Go ecosystem. Vulert records 4 vulnerabilities for it across 93 releases, from May 2026 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 M1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 24 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/go-git/go-billy/v5 v5.9.2 i

Updated on 23 Oct 2026

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

Package health score 71/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • 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 v5.9.2 — affected i
  • Vulnerabilities on record 4 over 1 year · 4 in the last year i
  • Latest disclosure 24 Jul 2026 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Stars 432 i
  • OpenSSF scorecard 7/10 i
  • Last release 3 months ago 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/go-git/go-billy/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.9.1 22 Jul 2026 H1 M1 U2 Apache-2.0 Yes Details →
v5.9.2 22 Jul 2026 H1 M1 U2 Apache-2.0 Yes Details →
v5.9.0 06 May 2026 H1 M1 U2 Apache-2.0 Yes Details →
v5.8.1-0.20260506061021-07f2a0bf50e4 06 May 2026 H1 M1 U2 Apache-2.0 Yes Details →
v5.8.1-0.20260505115358-427b27f32f22 05 May 2026 H1 M1 U2 Apache-2.0 Yes Details →
v5.8.1-0.20260503214341-8bf3d05b91ce 03 May 2026 H1 M1 U2 Apache-2.0 Yes Details →
v5.8.1-0.20260407233109-416e0a5b21a8 07 Apr 2026 H1 M1 U2 Apache-2.0 Yes Details →
v5.8.0 24 Feb 2026 H1 M1 U2 Apache-2.0 Yes Details →
v5.7.0 06 Dec 2025 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20250112183528-18f878617b0e 12 Jan 2025 H1 M1 U2 Apache-2.0 Yes Details →
v5.6.2 10 Jan 2025 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20250106225706-6f2032099ad7 06 Jan 2025 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20241228185033-a0a6b08d9032 28 Dec 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.6.1 28 Dec 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.6.1-0.20241125180829-9ca623cfaa35 25 Nov 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.6.1-0.20241118170737-9706761cf937 18 Nov 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.6.1-0.20241111173821-1bb3aa54c166 11 Nov 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.6.1-0.20241028170023-18393135c605 28 Oct 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20241008101053-371e232676ac 08 Oct 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.6.0 08 Oct 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240930170605-5f263c979534 30 Sep 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240927131424-c1ee0b97d109 27 Sep 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240924073428-9745bbbd3431 24 Sep 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240917100134-b0c83cae0621 17 Sep 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240902165505-04d471ab6285 02 Sep 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240828070317-59c50b000c7a 28 Aug 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240819193939-9b484184bdcc 19 Aug 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240814154544-eaed248167f1 14 Aug 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240809170954-dd96d0b9a95f 09 Aug 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240805213603-fac749f7395a 05 Aug 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.0.0-20240804231525-dc481f5289ba 04 Aug 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240804231525-dc481f5289ba 04 Aug 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240731070511-69f6dc8f1196 31 Jul 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240729185128-9e5678e36691 29 Jul 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240722162406-7e4a30ca167c 22 Jul 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240715164247-b2bff47672df 15 Jul 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240704161215-1f873dd385b9 04 Jul 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240701174852-839dcd3ad096 01 Jul 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240618082938-888ac091c08c 18 Jun 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240610172512-3572e16a925f 10 Jun 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240606065907-066ee277a284 06 Jun 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240604072145-a2ac1f0fea3a 04 Jun 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240520223002-8c848eaedfa9 20 May 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240514075308-8f1b719cb6a2 14 May 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240501073131-eafb735e5b54 01 May 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240428193043-b7d9906f197a 28 Apr 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240427062058-cfca65904524 27 Apr 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240427054813-8453aa90c6ec 27 Apr 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240419125355-72e896612ab3 19 Apr 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240327091054-4d0d7f0db7ba 27 Mar 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240316070245-0bb341d08d06 16 Mar 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240315223650-8a51f1289c6b 15 Mar 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20240306082043-d0a64abfa594 06 Mar 2024 H1 M1 U2 Apache-2.0 Yes Details →
v5.0.0-20231211202411-9f60ea941235 11 Dec 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20231211202411-9f60ea941235 11 Dec 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.0.0-20231207211727-9fe7b83bdb1e 07 Dec 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20231207211727-9fe7b83bdb1e 07 Dec 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.0.0-20231206230401-63a02cc06fe3 06 Dec 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20231206230401-63a02cc06fe3 06 Dec 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20231120210930-d23351b68761 20 Nov 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20231028015345-b30fba39a598 28 Oct 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20231013223915-c30186cdb271 13 Oct 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.1-0.20231011231026-5335bec55a87 11 Oct 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.4.2-0.20230911161450-5c1dfec7a041 11 Sep 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.5.0 11 Sep 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.4.2-0.20230903200408-ca80085d5257 03 Sep 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.0.0-20230829212759-74a6e6029a0b 29 Aug 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.4.2-0.20230829212759-74a6e6029a0b 29 Aug 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.4.2-0.20230825153425-1d4d3d3bf1a2 25 Aug 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.4.2-0.20230824145605-3c59de8dc969 24 Aug 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.4.2-0.20230525084112-326c59f06402 25 May 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.0.0-20230205111430-ed16d7ba55f9 05 Feb 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.4.1 05 Feb 2023 H1 M1 U2 Apache-2.0 Yes Details →
v5.3.2-0.20221219163930-1b88f62a6a85 19 Dec 2022 H1 M1 U2 Apache-2.0 Yes Details →
v5.4.0 19 Dec 2022 H1 M1 U2 Apache-2.0 Yes Details →
v5.0.0-20210804024030-7ab80d7c013d 04 Aug 2021 H1 M1 U2 Apache-2.0 Yes Details →
v5.3.2-0.20210804024030-7ab80d7c013d 04 Aug 2021 H1 M1 U2 Apache-2.0 Yes Details →
v5.3.2-0.20210603180030-213e20d29a0d 03 Jun 2021 H1 M1 U2 Apache-2.0 Yes Details →
v5.3.2-0.20210603175951-e0768be422ff 03 Jun 2021 H1 M1 U2 Apache-2.0 Yes Details →
v5.3.1 02 May 2021 H1 M1 U2 Apache-2.0 Yes Details →
v5.2.1-0.20210428225051-af7e4ac12d42 28 Apr 2021 H1 M1 U2 Apache-2.0 Yes Details →
v5.3.0 28 Apr 2021 H1 M1 U2 Apache-2.0 Yes Details →
v5.2.1-0.20210428041909-40a2dbe39fc6 28 Apr 2021 H1 M1 U2 Apache-2.0 Yes Details →
v5.1.1-0.20210422001516-42ead41a46a4 22 Apr 2021 H1 M1 U2 Apache-2.0 Yes Details →
v5.2.0 22 Apr 2021 H1 M1 U2 Apache-2.0 Yes Details →
v5.1.1-0.20210421212551-609712c172a2 21 Apr 2021 H1 M1 U2 Apache-2.0 Yes Details →
v5.1.1-0.20210419034928-36058ceb30d2 19 Apr 2021 H1 M1 U2 Apache-2.0 Yes Details →
v5.0.1-0.20210310065046-3d7f61fe9ffd 10 Mar 2021 H1 M1 U2 Apache-2.0 Yes Details →
v5.1.0 10 Mar 2021 H1 M1 U2 Apache-2.0 Yes Details →
v5.0.1-0.20200914114554-78517ac908a2 14 Sep 2020 H1 M1 U2 Apache-2.0 Yes Details →
v5.0.0-20200309202203-d7a8afccaed2 09 Mar 2020 H1 M1 U2 Apache-2.0 Yes Details →
v5.0.1-0.20200309202203-d7a8afccaed2 09 Mar 2020 H1 M1 U2 Apache-2.0 Yes Details →
v5.0.0 09 Mar 2020 H1 M1 U2 Apache-2.0 Yes Details →

All 93 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 4

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

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/go-git/go-billy/v5

Is github.com/go-git/go-billy/v5 safe to use?

Vulert records 4 vulnerabilities for github.com/go-git/go-billy/v5 in Go: 0 critical, 1 high, 1 medium and 0 low, plus 2 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/go-git/go-billy/v5's Vulert package health score?

Vulert scores github.com/go-git/go-billy/v5 71/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/go-git/go-billy/v5 affected?

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

Which version of github.com/go-git/go-billy/v5 should I use?

v5.9.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/go-git/go-billy/v5 have?

4 vulnerabilities are recorded for github.com/go-git/go-billy/v5 in the Go ecosystem: 0 critical, 1 high, 1 medium and 0 low, plus 2 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/go-git/go-billy/v5 vulnerabilities disclosed?

4 vulnerabilities were recorded for github.com/go-git/go-billy/v5 in the last 12 months, and the oldest entry in this database dates to 13 May 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/go-git/go-billy/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/go-git/go-billy/v5 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/go-git/go-billy/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.