RHSA-2026:3974HighCVSS 7.5

Red Hat Security Advisory: git-lfs security update

Published
March 9, 2026
Last Modified
September 4, 2026

🔗 CVE IDs covered (2)

CVE-2025-61726 →CVE-2025-61729 →

📋 Description

CVE-2025-61726 — golang: net/url: Memory exhaustion in query parameter parsing in net/url CVE-2025-61729 — crypto/x509: golang: Denial of Service due to excessive resource consumption via crafted certificate

🎯 Affected products13

  • Red Hat Enterprise Linux AppStream E4S (v.8.8)
  • Red Hat Enterprise Linux AppStream TUS (v.8.8)
  • git-lfs-0:3.2.0-2.el8_8.6.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8)
  • git-lfs-0:3.2.0-2.el8_8.6.src as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8)
  • git-lfs-0:3.2.0-2.el8_8.6.src as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8)
  • git-lfs-0:3.2.0-2.el8_8.6.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8)
  • git-lfs-0:3.2.0-2.el8_8.6.x86_64 as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8)
  • git-lfs-debuginfo-0:3.2.0-2.el8_8.6.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8)
  • git-lfs-debuginfo-0:3.2.0-2.el8_8.6.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8)
  • git-lfs-debuginfo-0:3.2.0-2.el8_8.6.x86_64 as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8)
  • git-lfs-debugsource-0:3.2.0-2.el8_8.6.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8)
  • git-lfs-debugsource-0:3.2.0-2.el8_8.6.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.8.8)
  • git-lfs-debugsource-0:3.2.0-2.el8_8.6.x86_64 as a component of Red Hat Enterprise Linux AppStream TUS (v.8.8)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.

🔗 References (5)