# CVE-2026-59919: Netty: HAProxy V1 Protocol CRLF Injection via AF_UNIX Address > Attackers can inject CRLF sequences into HAProxy V1 headers via AF_UNIX addresses, spoofing client IPs to downstream servers. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 29 Jul 2026 - **Updated:** 29 Jul 2026 - **Also known as:** CLEANSTART-2026-DB56545, CLEANSTART-2026-NC41949, DEBIAN-CVE-2026-59919, ECHO-970b-879f-6b93, GHSA-wh89-7897-x99h, MINI-29rj-fwgw-2q93, MINI-2g42-82xp-r7m3, MINI-36qx-ffv7-9cpf, MINI-3qp5-9cc4-wh2f, MINI-4c7x-pvqm-j894, MINI-52g5-fjw3-v5q8, MINI-52rx-m5xx-jcxr, MINI-59rh-vv9m-29v8, MINI-5rpp-h6v3-v838, MINI-6g39-wh4j-42f7, MINI-6gjv-42qh-g5c4, MINI-7xw5-7f58-v9jm, MINI-8282-6h85-xrqx, MINI-9c7v-6pj8-7p66, MINI-9xg7-2h4c-q4q8, MINI-cqqf-xx4w-7449, MINI-fgcp-896m-w5x4, MINI-fx43-qwvx-xhqw, MINI-fx48-h7w4-8f43, MINI-fx8g-cm74-qcch, MINI-g2x4-jqvj-pm23, MINI-g7w5-hcf2-cwwx, MINI-gcx2-q9mj-pp6q, MINI-hf8r-9c38-739f, MINI-jcpv-mp23-vwqf, MINI-mqmq-wg57-cfx2, MINI-q7hc-x8v4-73gv, MINI-qr2f-xpv3-4gq2, MINI-qxmw-6gqr-9v5f, MINI-rf79-63c3-q24j, MINI-rxh7-9hr5-rv6r, MINI-rxvr-9f8g-rpwx, MINI-rxw4-2gjv-cprr, MINI-v5fj-ghw9-2cjf, MINI-vr47-wpf4-625x, MINI-vvmq-29qp-4g86, MINI-x6hf-cjhp-hxxg, MINI-xf74-m285-p95r, UBUNTU-CVE-2026-59919 ## What is CVE-2026-59919? CVE-2026-59919 is a medium-severity vulnerability in Netty Netty, published on 29 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Netty is an asynchronous, event-driven network application framework. In versions prior to 4.1.136.Final and 4.2.16.Final, Netty's HAProxy encoder ( HAProxyMessageEncoder ) writes AF_UNIX source and destination socket addresses into the HAProxy V1 text protocol without validating them for CRLF characters, so an attacker who controls an AF_UNIX address can inject  \r\n  sequences and split the single PROXY header into multiple lines. This is possible because the V1 protocol uses CRLF as its line terminator and, unlike IPv4/IPv6 addresses whose format checks implicitly reject CRLF, AF_UNIX addresses are only validated for length (up to 108 bytes), allowing a forged second PROXY header line that spoofs the client source/destination IP to a downstream server or load balancer. The issue is fixed in versions 4.1.136.Final and 4.2.16.Final. Weakness: CWE-93 (Improper Neutralization of CRLF Sequences) ## Which versions are affected by CVE-2026-59919? 4 open source packages ship an affected version, including io.netty:netty-codec-haproxy. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `io.netty:netty-codec-haproxy` | Maven | All versions | 4.1.136.Final | | `io.netty:netty-codec-haproxy` | Maven | All versions | 4.1.136.Final | | `io.netty:netty-codec-haproxy` | Maven | From 4.2.0.Final | 4.2.16.Final | | `io.netty:netty-codec-haproxy` | Maven | From 4.2.0.Final | 4.2.16.Final | Products: Netty Netty. ## How do I fix CVE-2026-59919? Upgrade io.netty:netty-codec-haproxy to a fixed version for your release line: 4.1.136.Final or 4.2.16.Final. ## Is CVE-2026-59919 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59919 exists. ## Other vulnerabilities in Netty Netty - [CVE-2026-75595](https://insights.sbomify.com/CVE-2026-75595/): Netty: SNI Routing Bypass via Fragmented TLS ClientHello Causing Fallback to Default SslContext (critical 9.1) - [CVE-2026-75596](https://insights.sbomify.com/CVE-2026-75596/): Netty: Fragmented ClientHello records trigger quadratic pre-handshake reassembly in default SNI parsing (high 8.7) - [CVE-2026-59901](https://insights.sbomify.com/CVE-2026-59901/): Netty Bzip2Decoder: Infinite Loop in RLE State Machine Leads to Event-Loop Thread Hang (high 8.7) - [CVE-2026-55851](https://insights.sbomify.com/CVE-2026-55851/): Netty codec-haproxy: Signed-Byte Sentinel Collision in HAProxyMessageDecoder Leads to Unbounded Memory Exhaustion (high 8.7) - [CVE-2026-56745](https://insights.sbomify.com/CVE-2026-56745/): Netty SpdyHttpDecoder: ByteBuf Reference Leak on RST_STREAM Leads to Native Memory Exhaustion (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-59919 and fix it if it is affected. What it is: CVE-2026-59919 is a medium-severity vulnerability in Netty Netty, published on 29 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59919 exists. Affected packages and fixed versions: - io.netty:netty-codec-haproxy (Maven): affected all versions; fixed in 4.1.136.Final - io.netty:netty-codec-haproxy (Maven): affected all versions; fixed in 4.1.136.Final - io.netty:netty-codec-haproxy (Maven): affected from 4.2.0.Final; fixed in 4.2.16.Final - io.netty:netty-codec-haproxy (Maven): affected from 4.2.0.Final; fixed in 4.2.16.Final Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-59919/ (Markdown: https://insights.sbomify.com/CVE-2026-59919/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59919 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59919 - OSV: https://osv.dev/vulnerability/CVE-2026-59919 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-59919/ Summaries are generated and may contain mistakes; the official description above is the record.