CVE-2026-44740: go-billy: Lack of depth and cycle detection in symlink resolution may lead to infinite loops and resource exhaustion

Published May 13, 2026
·
Updated

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. 🙇

Other sources

Billy is an interface filesystem abstraction for Go. Prior to versions 5.9.0 and 6.0.0-alpha.1, 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. This issue has been patched in versions 5.9.0 and 6.0.0-alpha.1.

— MITRE

Affected Software

3 affected componentsFixes available
go/github.com/go-git/go-billy/v6<6.0.0-alpha.1
6.0.0-alpha.1
go/github.com/go-git/go-billy/v5<5.9.0
5.9.0
IBM Concert Software<=1.0-3.0.1.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/github.com/go-git/go-billy/v6 to a version that resolves this vulnerability.

    Fixed in 6.0.0-alpha.1
  2. Upgrade

    Upgrade go/github.com/go-git/go-billy/v5 to a version that resolves this vulnerability.

    Fixed in 5.9.0
  3. Upgrade

    Upgrade go-billy to a version that resolves this vulnerability.

    Fixed in 5.9.0
  4. Upgrade

    Upgrade go-billy to a version that resolves this vulnerability.

    Fixed in 6.0.0-alpha.1

Event History

May 13, 2026
Advisory Published
via GitHub·03:29 PM
Data Sourced
via GitHub·03:29 PM
DescriptionSeverityWeaknessAffected Software
Jun 1, 2026
CVE Published
via MITRE·04:04 PM
Data Sourced
via MITRE·04:04 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness
Jun 2, 2026
Data Sourced
via Red Hat·04:26 AM
DescriptionSeverityAffected Software
Oct 29, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-44740?

CVE-2026-44740 can lead to critical issues like panics, infinite loops, and excessive resource consumption due to improper handling of crafted input.

2

How do I fix CVE-2026-44740?

To fix CVE-2026-44740, upgrade to version 6.0.0-alpha.1 for go-git/go-billy/v6 or version 5.9.0 for go-git/go-billy/v5.

3

What components are affected by CVE-2026-44740?

CVE-2026-44740 affects the go-git/go-billy packages, specifically versions below 5.9.0 and 6.0.0-alpha.1.

4

What kind of vulnerabilities does CVE-2026-44740 involve?

CVE-2026-44740 involves vulnerabilities that allow for improper handling of input, potentially resulting in uncontrolled recursion and performance degradation.

5

Is there a risk of exploitation with CVE-2026-44740?

Yes, the vulnerabilities outlined in CVE-2026-44740 pose a risk of exploitation through crafted input, leading to significant system strain or crashes.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203