RHSA-2026:67319HighCVSS 8.2

Red Hat Security Advisory: git-lfs security update

Published
September 14, 2026
Last Modified
September 19, 2026

🔗 CVE IDs covered (11)

CVE-2026-39821 →CVE-2026-56859 →CVE-2026-56862 →CVE-2025-68121 →CVE-2026-32280 →CVE-2026-32282 →CVE-2026-32283 →CVE-2026-33818 →CVE-2026-56860 →CVE-2026-32281 →CVE-2026-33811 →

📋 Description

CVE-2025-68121 — crypto/tls: crypto/tls: Incorrect certificate validation during TLS session resumption CVE-2026-32280 — crypto/x509: crypto/tls: golang: Go: Denial of Service vulnerability in certificate chain building CVE-2026-32281 — crypto/x509: golang: Go crypto/x509: Denial of Service via inefficient certificate chain validation CVE-2026-32282 — golang: internal/syscall/unix: Root.Chmod can follow symlinks out of the root CVE-2026-32283 — crypto/tls: golang: Go crypto/tls: Denial of Service via multiple TLS 1.3 key update messages CVE-2026-33811 — net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME CVE-2026-33818 — encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal CVE-2026-39821 — golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing CVE-2026-56859 — encoding/xml: golang: Go: Denial of Service via XML decoding recursion depth issue CVE-2026-56860 — net/url: golang: golang net/url: Denial of Service from quadratic complexity in path resolution CVE-2026-56862 — crypto/tls: golang: Golang crypto/tls: Denial of Service via indefinite KeyUpdate messages

🎯 Affected products14

  • Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • git-lfs-0:3.2.0-2.el9_2.10.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • git-lfs-0:3.2.0-2.el9_2.10.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • git-lfs-0:3.2.0-2.el9_2.10.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • git-lfs-0:3.2.0-2.el9_2.10.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • git-lfs-0:3.2.0-2.el9_2.10.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • git-lfs-debuginfo-0:3.2.0-2.el9_2.10.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • git-lfs-debuginfo-0:3.2.0-2.el9_2.10.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • git-lfs-debuginfo-0:3.2.0-2.el9_2.10.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • git-lfs-debuginfo-0:3.2.0-2.el9_2.10.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • git-lfs-debugsource-0:3.2.0-2.el9_2.10.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • git-lfs-debugsource-0:3.2.0-2.el9_2.10.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • git-lfs-debugsource-0:3.2.0-2.el9_2.10.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)
  • git-lfs-debugsource-0:3.2.0-2.el9_2.10.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2)

✅ 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: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: To mitigate this issue, applications can be configured to use the pure Go DNS resolver instead of the `cgo` DNS resolver. This can be achieved by setting the `GODEBUG` environment variable to `netdns=go`. For example, to run a Go application with this mitigation: `GODEBUG=netdns=go /path/to/your/go/application`. This change may require restarting affected applications or services to take effect. Users should verify that this change does not negatively impact DNS resolution for their specific application environment. Workaround: Upgrade to a fixed golang.org/x/net release that includes the idna correction, via updated golang or dependent package rebuilds.

🔗 References (14)