Linux ·
openSUSE Leap · Security advisory · September 14, 2026
openSUSE Leap · Security advisory · September 14, 2026OPENSUSE-SU-2026:21841-1: hauler security update
OPENSUSE-SU-2026:21841-1, released September 14, 2026, fixes 7 CVEs in hauler (version 2.1.0-bp160.3.1). None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
7
None rated Critical
Exploited
0
None reported
Highest CVSS
7.5
Base score, 0 to 10
Highest EPSS
0.0064
50th percentile
Priority of the 7 CVEs
Patch now 0
Urgent 0
High 4
Routine 3
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| hauler | opensuse-leap 16.0 | 2.1.0-bp160.3.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-84445 | gRPC-Go: Denial of Service (DoS) via crash due to missing `:authority` and `Host` headers in the xDS servers | 7.5 | 0.0064 | None reported |
| High | CVE-2026-56855 | Prevent DoS on deadlocked established channel in golang.org/x/crypto/ssh | 7.5 | 0.0050 | None reported |
| High | CVE-2026-56854 | golang-go.crypto: The source-address critical option in the Permissions returned by an authentication callback was only enforced for th... | 7.5 | 0.0044 | None reported |
| High | CVE-2026-78662 | Prevent DoS on deadlocked undecided channel in golang.org/x/crypto/ssh | 7.5 | 0.0043 | None reported |
| Routine | CVE-2026-84304 | gRPC-Go: Heap Memory Exhaustion (OOM) via HTTP/2 DATA Frame Fragmentation | 4.4 | 0.0061 | None reported |
| Routine | CVE-2026-84303 | gRPC-Go: xDS RBAC HTTP Filter bypass via mixed-case Header Matching and gRFC A41 validation evasion | n/a | 0.0031 | None reported |
| Routine | CVE-2026-41888 | distribution: This update for distribution fixes the following issues: Security issues fixed: - CVE-2026-33186: google.golang.org... | n/a | 0.0029 | None reported |
Showing 1 to 7 of 7
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.