CVE-2026-44740

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

June 1, 2026

Last Modified

July 22, 2026

Advisory Details (3)

Auto-updated Jun 12, 2026
Patch available. Sources: github_release, github.
github Patch Available

Improper input handling may cause panics, infinite loops, or uncontrolled resource consumption · Advisory · go-git/go-billy · GitHub

https://github.com/go-git/go-billy/security/advisories/GHSA-m3xc-h892-ggx6
github_release Patch Available

v6.0.0-alpha.1

Patch available: go-git/go-billy v6.0.0-alpha.1 (pre-release)

https://github.com/go-git/go-billy/releases/tag/v6.0.0-alpha.1
github_release Patch Available

v5.9.0

Patch available: go-git/go-billy v5.9.0

https://github.com/go-git/go-billy/releases/tag/v5.9.0

Vendor Advisories for CVE-2026-44740(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(28)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatoadp/oadp-mustgather-rhel9:17888598962026-09-09redhat
redhatopenshift-gitops-1/gitops-rhel9-operator:17877295452026-09-03redhat
redhatcluster-observability-operator/perses-rhel9-operator:17875936972026-08-31redhat
redhatrhacm2/multicluster-operators-subscription-rhel9:17872635842026-08-26redhat
redhatrhacm2/multicluster-operators-subscription-rhel9:17871708302026-08-26redhat
redhatrhacm2/multicluster-operators-subscription-rhel9:17872421082026-08-26redhat
redhatmulticluster-engine/cluster-image-set-controller-rhel9:17869833622026-08-25redhat
redhatoadp/oadp-mustgather-rhel9:17869462942026-08-25redhat
redhatmulticluster-engine/cluster-image-set-controller-rhel9:17867646012026-08-25redhat
redhatrhacm2/multicluster-operators-subscription-rhel9:17869087772026-08-19redhat
redhatmulticluster-engine/cluster-image-set-controller-rhel9:17869119572026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17866295482026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17867031432026-08-18redhat
redhatexternal-secrets-operator/external-secrets-rhel9:17866146762026-08-13redhat
redhatrhacm2/kube-state-metrics-rhel9:17865493452026-08-12redhat
redhatoadp/oadp-mustgather-rhel9:17851773592026-08-06redhat
redhatrhtas/gitsign-rhel9:17853595472026-08-05redhat
redhatrhacm2/multicluster-operators-subscription-rhel9:17847401432026-07-29redhat
redhatmulticluster-engine/cluster-image-set-controller-rhel9:17846467862026-07-29redhat
redhatrhacm2/multicluster-operators-subscription-rhel9:17842295082026-07-28redhat
redhatmulticluster-engine/cluster-image-set-controller-rhel9:17846460262026-07-28redhat
redhatgrafana-0:9.2.10-32.el8_102026-07-27redhat
redhatrhtas/gitsign-rhel9:17839598192026-07-16redhat
redhatodf4/rook-ceph-rhel9-operator:17829342842026-07-09redhat
redhatrhacm2/submariner-rhel9-operator:17829331932026-07-08redhat
redhattrivy-main-0.72.0-0.1.hum12026-07-02redhat
redhatsyft-main-1.46.0-0.1.hum12026-06-29redhat
redhatgrype-main-0.115.0-0.1.hum12026-06-29redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 4 ecosystems)
Debian:14(2)
PackageVulnerable rangeFixed inDependents
golang-github-go-git-go-billy5.5.0-1, 5.5.0-2, 5.8.0-15.9.0-1—
golang-github-go-git-go-billy-v66~git20260226.45bd095-1, 6~git20260226.45bd095-26.0.0~alpha.1-1—
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/go-git/go-billy/v5—5.9.0—
github.com/go-git/go-billy/v6—6.0.0-alpha.1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-github-go-git-go-billy5.3.1-3 ... 5.9.1-1 (6 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-github-go-git-go-billy5.5.0-1, 5.5.0-2, 5.8.0-1, 5.9.0-1, 5.9.1-1——

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(12)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 167 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-14 06:09 UTCEG score recompute
  6. 2026-09-14 06:09 UTCVendor advisory
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-13 00:36 UTCOSV refresh
  9. 2026-09-12 15:01 UTCEPSS rescore
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 09:37 UTCEPSS rescore
  12. 2026-09-10 09:34 UTCEPSS rescore
  13. 2026-09-08 22:00 UTCEPSS rescore
  14. 2026-09-07 16:01 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-04 05:06 UTCEPSS rescore
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 13:54 UTCEPSS rescore
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-25 03:56 UTCEG score recompute
Show 75 more
  1. 2026-08-25 03:56 UTCVendor advisory
  2. 2026-08-23 13:55 UTCEG score recompute
  3. 2026-08-23 13:55 UTCVendor advisory
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 14:52 UTCEG score recompute
  7. 2026-08-21 14:52 UTCVendor advisory
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 10:18 UTCEG score recompute
  10. 2026-08-20 10:18 UTCVendor advisory
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 04:58 UTCEG score recompute
  15. 2026-08-17 04:58 UTCVendor advisory
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 02:22 UTCEG score recompute
  18. 2026-08-16 02:22 UTCVendor advisory
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 02:03 UTCEG score recompute
  21. 2026-08-15 02:03 UTCVendor advisory
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 04:21 UTCEG score recompute
  24. 2026-08-14 04:21 UTCVendor advisory
  25. 2026-08-13 22:00 UTCEPSS rescore
  26. 2026-08-13 06:39 UTCEG score recompute
  27. 2026-08-13 06:39 UTCVendor advisory
  28. 2026-08-12 13:51 UTCEPSS rescore
  29. 2026-08-12 08:56 UTCEG score recompute
  30. 2026-08-12 08:56 UTCVendor advisory
  31. 2026-08-11 07:14 UTCEG score recompute
  32. 2026-08-11 07:14 UTCVendor advisory
  33. 2026-08-11 00:00 UTCEPSS rescore
  34. 2026-08-10 09:32 UTCEG score recompute
  35. 2026-08-10 09:32 UTCVendor advisory
  36. 2026-08-09 13:46 UTCEPSS rescore
  37. 2026-08-09 11:50 UTCEG score recompute
  38. 2026-08-09 11:50 UTCVendor advisory
  39. 2026-08-08 16:37 UTCEPSS rescore
  40. 2026-08-08 13:51 UTCEG score recompute
  41. 2026-08-08 13:51 UTCVendor advisory
  42. 2026-08-07 16:09 UTCVendor advisory
  43. 2026-08-06 18:25 UTCEG score recompute
  44. 2026-08-06 18:25 UTCVendor advisory
  45. 2026-08-06 13:46 UTCEPSS rescore
  46. 2026-08-05 20:39 UTCEG score recompute
  47. 2026-08-05 20:39 UTCVendor advisory
  48. 2026-08-05 19:17 UTCEPSS rescore
  49. 2026-08-04 22:40 UTCEG score recompute
  50. 2026-08-04 22:40 UTCVendor advisory
  51. 2026-08-04 15:10 UTCEPSS rescore
  52. 2026-08-04 10:38 UTCEPSS rescore
  53. 2026-08-03 15:50 UTCEG score recompute
  54. 2026-08-03 15:50 UTCVendor advisory
  55. 2026-08-03 10:36 UTCEPSS rescore
  56. 2026-08-02 11:20 UTCEG score recompute
  57. 2026-08-02 11:20 UTCVendor advisory
  58. 2026-08-02 02:27 UTCEPSS rescore
  59. 2026-08-01 13:38 UTCEG score recompute
  60. 2026-08-01 13:38 UTCVendor advisory
  61. 2026-08-01 04:16 UTCEPSS rescore
  62. 2026-07-31 05:43 UTCEG score recompute
  63. 2026-07-31 05:43 UTCVendor advisory
  64. 2026-07-30 16:28 UTCEPSS rescore
  65. 2026-07-30 01:30 UTCEPSS rescore
  66. 2026-07-29 11:13 UTCEG score recompute
  67. 2026-07-29 11:13 UTCVendor advisory
  68. 2026-07-28 15:36 UTCEPSS rescore
  69. 2026-07-28 03:52 UTCEG score recompute
  70. 2026-07-28 03:52 UTCVendor advisory
  71. 2026-07-27 14:13 UTCEPSS rescore
  72. 2026-07-26 23:41 UTCEG score recompute
  73. 2026-07-26 23:41 UTCVendor advisory
  74. 2026-07-26 14:54 UTCEPSS rescore
  75. 2026-07-26 14:54 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-44740?
CVE-2026-44740 is a medium vulnerability published on June 1, 2026. 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…
When was CVE-2026-44740 disclosed?
CVE-2026-44740 was first published in the National Vulnerability Database on June 1, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44740 actively exploited?
CVE-2026-44740 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.2% of all scored CVEs.
What is the CVSS score of CVE-2026-44740?
CVE-2026-44740 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-44740?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44740, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44740

Explore →

Is Your Infrastructure Affected by CVE-2026-44740?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs