# SUSE-SU-2026:2308-1: Security update for 2 packages

SUSE-SU-2026:2308-1, released June 9, 2026, fixes 12 CVEs across 2 products. None of them is reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/fix/linux/suse-su-2026-2308-1
- Platform: Linux
- Released: Jun 9, 2026
- Priority: High (Closes CVE-2026-42578, high severity)
- CVEs: 12, exploited: 0, on CISA KEV: 0
- Vendor advisory: https://osv.dev/vulnerability/SUSE-SU-2026:2308-1

## Applies to

| Product | Release | Fixed in |
|---|---|---|
| [netty](https://patchblox.com/security/data/product/linux/netty.md) | sles 15.7 | 4.1.133-150200.4.46.1 |
| [netty-tcnative](https://patchblox.com/security/data/product/linux/netty-tcnative.md) | sles 15.6 | 2.0.77-150200.3.39.1 |
| [netty-tcnative](https://patchblox.com/security/data/product/linux/netty-tcnative.md) | sles 15.7 | 2.0.77-150200.3.39.1 |

## CVEs this fix closes

| CVE | Priority | Title | CVSS | EPSS | Exploitation |
|---|---|---|---:|---:|---|
| [CVE-2026-42578](https://patchblox.com/security/data/cve/CVE-2026-42578.md) | High | netty-tcnative: HTTP Header Injection via HttpProxyHandler Disabled Validation in Netty (bsc#1265243). | 7.5 | 0.0107 |  |
| [CVE-2026-42579](https://patchblox.com/security/data/cve/CVE-2026-42579.md) | High | netty-tcnative: DNS codec does not enforce RFC 1035 domain name constraints during either encoding or decoding | 7.5 | 0.0101 |  |
| [CVE-2026-42587](https://patchblox.com/security/data/cve/CVE-2026-42587.md) | High | netty-tcnative: HttpContentDecompressor maxAllocation bypass via Content-Encoding: br/zstd/snappy enables | 7.5 | 0.0099 |  |
| [CVE-2026-42584](https://patchblox.com/security/data/cve/CVE-2026-42584.md) | High | netty-tcnative: improper handling of inbound responses in `HttpClientCodec` can lead to response desynchronization | 7.3 | 0.0084 |  |
| [CVE-2026-42581](https://patchblox.com/security/data/cve/CVE-2026-42581.md) | High | netty-tcnative: TE+CL header coexistence in HTTP/1.0 requests bypasses smuggling sanitization (bsc#1265277). | 7.2 | 0.0063 |  |
| [CVE-2026-44248](https://patchblox.com/security/data/cve/CVE-2026-44248.md) | Routine | netty-tcnative: Netty is an asynchronous, event-driven network application framework (bsc#1265294). | n/a | 0.0056 |  |
| [CVE-2026-42583](https://patchblox.com/security/data/cve/CVE-2026-42583.md) | Routine | netty-tcnative: resource exhaustion and possible denial of service via `Lz4FrameDecoder` (bsc#1265279). | n/a | 0.0046 |  |
| [CVE-2026-42582](https://patchblox.com/security/data/cve/CVE-2026-42582.md) | Routine | netty-tcnative: HTTP/3 QPACK literal unbounded allocation (bsc#1265318). | n/a | 0.0044 |  |
| [CVE-2026-42580](https://patchblox.com/security/data/cve/CVE-2026-42580.md) | Routine | netty-tcnative: chunk size parser silently overflows int and enables request smuggling attacks (bsc#1265273). | n/a | 0.0038 |  |
| [CVE-2026-41417](https://patchblox.com/security/data/cve/CVE-2026-41417.md) | Routine | netty-tcnative: missing validations leads to HTTP request smuggling and RTSP request injection via start-line | n/a | 0.0032 |  |
| [CVE-2026-42585](https://patchblox.com/security/data/cve/CVE-2026-42585.md) | Routine | netty-tcnative: Netty is an asynchronous, event-driven network application framework (bsc#1265292). | 6.5 | 0.0027 |  |
| [CVE-2026-42586](https://patchblox.com/security/data/cve/CVE-2026-42586.md) | Routine | netty-tcnative: CRLF Injection in Netty Redis Codec Encoder (bsc#1265245). | n/a | 0.0022 |  |

---

Data as of 2026-11-11T01:43:54Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

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.