Linux · SUSE Linux Enterprise · Security advisory · July 8, 2026
SUSE-SU-2026:2802-1: Security update for 2 packages
SUSE-SU-2026:2802-1, released July 8, 2026, fixes 18 CVEs across 2 products. None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
18
None rated Critical
Exploited
0
None reported
Highest CVSS
8.7
Base score, 0 to 10
Highest EPSS
0.0099
62nd percentile
Priority of the 18 CVEs
Patch now 0
Urgent 0
High 5
Routine 13
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| netty | sles 15.7 | 4.1.135-150200.4.50.1 |
| netty-tcnative | sles 15.6 | 2.0.79-150200.3.45.1 |
| netty-tcnative | sles 15.7 | 2.0.79-150200.3.45.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-44249 | eap8-eap-product-conf-parent: Netty is a network application framework for development of protocol servers and clients | 8.1 | 0.0099 | None reported |
| High | CVE-2026-45416 | eap8-eap-product-conf-parent: Netty is a network application framework for development of protocol servers and clients | 7.5 | 0.0092 | None reported |
| High | CVE-2026-50010 | eap8-eap-product-conf-parent: Netty is a network application framework for development of protocol servers and clients | 7.5 | 0.0049 | None reported |
| High | CVE-2026-47691 | eap8-eap-product-conf-parent: Netty is a network application framework for development of protocol servers and clients | 8.7 | 0.0037 | None reported |
| High | CVE-2026-45674 | eap8-eap-product-conf-parent: Netty is a network application framework for development of protocol servers and clients | 8.7 | 0.0029 | None reported |
| Routine | CVE-2026-48043 | netty-tcnative: netty-codec-http2: Denial of Service due to resource leak (bsc#1268257). | n/a | 0.0075 | None reported |
| Routine | CVE-2026-48006 | netty-tcnative: netty-codec-redis: Netty's Lack of Lifecycle Cleanup Leads to Pooled ByteBuf Leak in | n/a | 0.0074 | None reported |
| Routine | CVE-2026-48059 | netty-tcnative: netty-codec-haproxy: Denial of Service via memory leak from crafted PROXY protocol headers | n/a | 0.0063 | None reported |
| Routine | CVE-2026-44893 | netty-tcnative: netty-codec-haproxy: Denial of Service via malformed HAProxy message (bsc#1268244). | n/a | 0.0062 | None reported |
| Routine | CVE-2026-46340 | netty-tcnative: netty-transport-sctp: Denial of Service due to unbounded memory growth from SctpMessage fragments | n/a | 0.0061 | None reported |
| Routine | CVE-2026-44250 | netty-tcnative: Memory Exhaustion in RedisArrayAggregator due to Deeply Nested Arrays (bsc#1268169). | n/a | 0.0046 | None reported |
| Routine | CVE-2026-44890 | netty-tcnative: Unbounded Direct Memory Consumption in RedisDecoder (bsc#1268170). | n/a | 0.0046 | None reported |
| Routine | CVE-2026-50011 | netty-tcnative: Unbounded pre-allocation in RedisArrayAggregator from RESP array length (bsc#1268260). | n/a | 0.0046 | None reported |
| Routine | CVE-2026-50560 | netty-tcnative: Netty susceptible to HTTP/2 Reset Attack with different on-the-wire signature (bsc#1268262). | n/a | 0.0040 | None reported |
| Routine | CVE-2026-47244 | netty-tcnative: HTTP/2: Advertised MAX_CONCURRENT_STREAMS not enforced (bsc#1268251). | n/a | 0.0038 | None reported |
| Routine | CVE-2026-45673 | netty-tcnative: netty-resolver-dns: DNS Cache Poisoning via predictable transaction IDs (bsc#1268248). | n/a | 0.0032 | None reported |
| Routine | CVE-2026-50020 | netty-tcnative: HttpObjectDecoder skips arbitrary initial control characters when only initial CRLF characters are | n/a | 0.0023 | None reported |
| Routine | CVE-2026-45536 | netty: Unix-socket fd receive leaks descriptors when peer sends two at once (bsc#1268247). | n/a | 0.0014 | None reported |
Showing 1 to 18 of 18
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.