Linux · 
Red Hat · Security advisory · May 15, 2026
Red Hat · Security advisory · May 15, 2026RHSA-2026:19350: git-lfs security update
RHSA-2026:19350, released May 15, 2026, fixes 8 CVEs in git-lfs (version 0:3.7.1-4.el9_8). None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
8
None rated Critical
Exploited
0
None reported
Highest CVSS
9.1
Base score, 0 to 10
Highest EPSS
0.0067
52nd percentile
Priority of the 8 CVEs
Patch now 0
Urgent 0
High 7
Routine 1
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| git-lfs | RHEL 9 | 0:3.7.1-4.el9_8 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-32283 | Unauthenticated TLS 1.3 KeyUpdate record can cause persistent connection retention and DoS in crypto/tls | 9.1 | 0.0063 | None reported |
| High | CVE-2026-32280 | Unexpected work during chain building in crypto/x509 | 9.1 | 0.0063 | None reported |
| High | CVE-2024-45341 | git-lfs: Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text poi... | 7.5 | 0.0056 | None reported |
| High | CVE-2025-47906 | git-lfs: Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text poi... | 7.5 | 0.0055 | None reported |
| High | CVE-2026-32281 | Inefficient policy validation in crypto/x509 | 9.1 | 0.0036 | None reported |
| High | CVE-2026-33810 | Case-sensitive excludedSubtrees name constraints cause Auth Bypass in crypto/x509 | 9.1 | 0.0035 | None reported |
| High | CVE-2026-32282 | TOCTOU permits root escape on Linux via Root.Chmod in os in internal/syscall/unix | 9.1 | 0.0030 | None reported |
| Routine | CVE-2025-4673 | Sensitive headers not cleared on cross-origin redirect in net/http | 6.8 | 0.0067 | None reported |
Showing 1 to 8 of 8
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.