Skip to content
Fencer Intel
high 8.1

CVE-2026-44973 json

Billy: Path traversal vulnerabilities

published 5mo ago modified last mo. also GHSA-qw64-3x98-g7q2 , GO-2026-5597 , EUVD-2026-33071

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits
0
none known

Summary

Billy is an interface filesystem abstraction for Go. Prior to 5.9.0, multiple path traversal issues exist across different components of go-billy. Insufficient path sanitization and boundary enforcement may allow crafted paths (e.g., using ..) to escape intended base directories. While go-billy was not originally designed to provide a strong security boundary, some of these issues were inconsistent across some of the built-in implementations. This results in scenarios where applications relying on go-billy for some level of isolation may inadvertently expose access to unintended filesystem locations. This vulnerability is fixed in 5.9.0.

Patch / fix

  • go github.com/go-git/go-billy/v5 5.9.0
  • go github.com/go-git/go-billy/v6 6.0.0-alpha.1
  • golang-github-go-git-go-billy Debian 14 5.9.0-1
  • golang-github-go-git-go-billy-v6 Debian 14 6.0.0~alpha.1-1

debian advisories DEBIAN-CVE-2026-44973

  • govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260727T201416-160000.1.1

suse advisories SUSE-SU-2026:23216-1SUSE-SU-2026:23227-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260727T201416-160000.1.1

opensuse advisories openSUSE-SU-2026:21551-1

Is CVE-2026-44973 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-44973 updated cvss 8.1

github.com/go-git/go-billy: Go-billy: Arbitrary file access due to path traversal vulnerability

  • Red Hat Multicluster Engine for Kubernetes multicluster-engine/assisted-service-9-rhel9
    affected: no fix planned “Will not fix”
  • Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/multicluster-operators-subscription-rhel9
    affected: no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/go-git/go-billy/v5
<5.9.0
5.9.0
go github.com/go-git/go-billy/v6
<6.0.0-alpha.1
6.0.0-alpha.1

Affected products

  • go-git go-billy

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.