CVE-2026-62380 Netty before 4.2.16.Final SOCKS Proxy Null Byte Injection
Attackers can inject null bytes or CRLF into SOCKS proxy fields to spoof domains or alter authentication data in Netty applications.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-62380?
CVE-2026-62380 is a medium-severity vulnerability in Netty Netty, published on 22 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Netty (io.netty:netty-codec-socks) versions 4.2.0.Final through 4.2.16.Final and 4.1.x through 4.1.136.Final contain null byte, CRLF, and credential injection vulnerabilities in the SOCKS4 (Socks4ClientEncoder) and SOCKS5 (Socks5ClientEncoder) client encoders, which fail to validate domain address and authentication (username/password) fields. An attacker able to control these fields can inject null bytes or CRLF characters to truncate or alter values, potentially enabling domain spoofing, SOCKS4 userid truncation, authentication data injection, and protocol confusion. Fixed in 4.2.17.Final and 4.1.137.Final.
Weakness: CWE-626
Which versions are affected by CVE-2026-62380?
It affects 1 product.
Products include Netty Netty.
How do I fix CVE-2026-62380?
Upgrade to a fixed version.
Is CVE-2026-62380 being exploited?
There is no known exploitation of CVE-2026-62380 in the wild and no public exploit code.
Other vulnerabilities in Netty Netty
- CVE-2026-75595 Netty: SNI Routing Bypass via Fragmented TLS ClientHello Causing Fallback to Default SslContext
- CVE-2026-75596 Netty: Fragmented ClientHello records trigger quadratic pre-handshake reassembly in default SNI parsing
- CVE-2026-59901 Netty Bzip2Decoder: Infinite Loop in RLE State Machine Leads to Event-Loop Thread Hang
- CVE-2026-55851 Netty codec-haproxy: Signed-Byte Sentinel Collision in HAProxyMessageDecoder Leads to Unbounded Memory Exhaustion
- CVE-2026-56745 Netty SpdyHttpDecoder: ByteBuf Reference Leak on RST_STREAM Leads to Native Memory Exhaustion
Sources
Also known as CLEANSTART-2026-BC54924, CLEANSTART-2026-NB43165, CLEANSTART-2026-PK97624, CLEANSTART-2026-VB05004, CLEANSTART-2026-VD69518, CLEANSTART-2026-YC22300 and 4 more.