Answer in brief
CVE-2026-44740 records a Medium severity (CVSS 6.5) vulnerability in go-billy: Lack of depth and cycle detection in symlink resolution may lead to infinite loops and resource exhaustion. The current sources do not mark it as known exploited. The current feed maps github.com/go-git/go-billy/v5 (go), github.com/go-git/go-billy/v5 (go), github.com/go-git/go-billy/v6 (go), github.com/go-git/go-billy/v6 (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps github.com/go-git/go-billy/v5 (go), github.com/go-git/go-billy/v5 (go), github.com/go-git/go-billy/v6 (go), github.com/go-git/go-billy/v6 (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| github.com/go-git/go-billy/v5go | <5.9.0 | 5.9.0 |
| github.com/go-git/go-billy/v5go | >=0 <5.9.0 | 5.9.0 |
| github.com/go-git/go-billy/v6go | <6.0.0-alpha.1 | 6.0.0-alpha.1 |
| github.com/go-git/go-billy/v6go | >=0 <6.0.0-alpha.1 | 6.0.0-alpha.1 |
Published upstream
May 13, 2026
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Jun 11, 2026
### Impact Multiple components may improperly handle crafted or malformed input, resulting in panics, infinite loops, uncontrolled recursion, or excessive resource consumption. These issues arise from insufficient validation and missing safety mechanisms such as cycle detection, recursion limits, or defensive handling of unexpected states when processing untrusted repository data and filesystem structures. ### Patches Users should upgrade to a patched version in order to mitigate this vulnerability. Versions prior to `v5` are likely to be affected, users are recommended to upgrade to a supported `go-billy` version. ### Credits Thanks to @faran66 for finding and reporting this issue privately to the go-git project. ๐
Quoted source text, attributed separately from HOL analysis.