Io.netty:netty codec haproxy: Netty: HAProxy V1 Protocol CRLF Injection via AF_UNIX Address (CVE-2026-59919)
Netty's HAProxy protocol encoder in the io.netty.handler.codec.haproxy.HAProxyMessageEncoder component improperly handles AF_UNIX socket addresses by not validating for CRLF characters. This allows CRLF injection into the HAProxy V1 protocol header, splitting a single PROXY line into multiple lines and enabling client IP spoofing via a second injected PROXY header line. The vulnerability affects Netty versions 4.2.12.Final and earlier with the codec-haproxy module. The root cause is that AF_UNIX addresses are only checked for length (<=108 bytes) without CRLF validation, unlike IPv4/IPv6 addresses which are format-validated. Exploitation requires user-controlled AF_UNIX addresses used in constructing PROXY protocol headers sent downstream. No patch status is confirmed from the provided data.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-59919) exists in Netty's HAProxyMessageEncoder.encodeV1() method, which writes AF_UNIX socket addresses directly into the HAProxy V1 text protocol without checking for CRLF characters. Since the V1 protocol uses CRLF as line terminators, injected CRLF characters in the AF_UNIX source or destination address split the PROXY header into multiple lines, effectively injecting a second PROXY protocol header. The AF_UNIX address validation only enforces a maximum length of 108 bytes and does not validate content for CRLF sequences, unlike IPv4/IPv6 addresses that are format-validated to exclude CRLF. This flaw enables an attacker controlling AF_UNIX addresses to inject additional PROXY headers, potentially causing downstream servers or load balancers to accept spoofed client IP addresses. Exploitation requires that the application uses Netty's HAProxyMessageEncoder with user-controlled AF_UNIX addresses in PROXY protocol headers. No official patch or fix is referenced in the provided data.
Potential Impact
The vulnerability allows an attacker to perform client IP spoofing by injecting a second PROXY protocol header line via CRLF injection in AF_UNIX socket addresses. This can mislead downstream servers or load balancers into accepting false client IP information, potentially affecting access control, logging, or auditing mechanisms that rely on accurate client IP data. The impact is limited to scenarios where Netty's HAProxyMessageEncoder is used with AF_UNIX addresses containing attacker-controlled input and the encoded PROXY headers are sent to downstream components that parse the HAProxy V1 protocol.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using user-controlled input in AF_UNIX addresses when constructing HAProxy V1 protocol headers with Netty's HAProxyMessageEncoder. Validate or sanitize AF_UNIX addresses to exclude CRLF characters before encoding. Consider upgrading to a fixed version once released or applying custom input validation to prevent CRLF injection.
Io.netty:netty codec haproxy: Netty: HAProxy V1 Protocol CRLF Injection via AF_UNIX Address (CVE-2026-59919)
Description
Netty's HAProxy protocol encoder in the io.netty.handler.codec.haproxy.HAProxyMessageEncoder component improperly handles AF_UNIX socket addresses by not validating for CRLF characters. This allows CRLF injection into the HAProxy V1 protocol header, splitting a single PROXY line into multiple lines and enabling client IP spoofing via a second injected PROXY header line. The vulnerability affects Netty versions 4.2.12.Final and earlier with the codec-haproxy module. The root cause is that AF_UNIX addresses are only checked for length (<=108 bytes) without CRLF validation, unlike IPv4/IPv6 addresses which are format-validated. Exploitation requires user-controlled AF_UNIX addresses used in constructing PROXY protocol headers sent downstream. No patch status is confirmed from the provided data.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-59919) exists in Netty's HAProxyMessageEncoder.encodeV1() method, which writes AF_UNIX socket addresses directly into the HAProxy V1 text protocol without checking for CRLF characters. Since the V1 protocol uses CRLF as line terminators, injected CRLF characters in the AF_UNIX source or destination address split the PROXY header into multiple lines, effectively injecting a second PROXY protocol header. The AF_UNIX address validation only enforces a maximum length of 108 bytes and does not validate content for CRLF sequences, unlike IPv4/IPv6 addresses that are format-validated to exclude CRLF. This flaw enables an attacker controlling AF_UNIX addresses to inject additional PROXY headers, potentially causing downstream servers or load balancers to accept spoofed client IP addresses. Exploitation requires that the application uses Netty's HAProxyMessageEncoder with user-controlled AF_UNIX addresses in PROXY protocol headers. No official patch or fix is referenced in the provided data.
Potential Impact
The vulnerability allows an attacker to perform client IP spoofing by injecting a second PROXY protocol header line via CRLF injection in AF_UNIX socket addresses. This can mislead downstream servers or load balancers into accepting false client IP information, potentially affecting access control, logging, or auditing mechanisms that rely on accurate client IP data. The impact is limited to scenarios where Netty's HAProxyMessageEncoder is used with AF_UNIX addresses containing attacker-controlled input and the encoded PROXY headers are sent to downstream components that parse the HAProxy V1 protocol.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using user-controlled input in AF_UNIX addresses when constructing HAProxy V1 protocol headers with Netty's HAProxyMessageEncoder. Validate or sanitize AF_UNIX addresses to exclude CRLF characters before encoding. Consider upgrading to a fixed version once released or applying custom input validation to prevent CRLF injection.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-wh89-7897-x99h
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-59919"]
- Ecosystems
- ["Maven"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a6150d39c2644c7f8da06d2
Added to database: 07/22/2026, 23:22:59 UTC
Last enriched: 07/22/2026, 23:29:44 UTC
Last updated: 07/22/2026, 23:29:44 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.