CVE-2026-62380: Netty before 4.2.16.Final SOCKS Proxy Null Byte Injection

Published Aug 22, 2026
·
Updated

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.

Affected Software

1 affected component
Netty io.netty:netty-codec-socks>=4.2.0.Final<=4.2.16.Final, >=4.1.x<=4.1.136.Final

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade io.netty:netty-codec-socks to a version that resolves this vulnerability.

    Fixed in 4.2.17.Final
  2. Upgrade

    Upgrade io.netty:netty-codec-socks to a version that resolves this vulnerability.

    Fixed in 4.1.137.Final

Event History

Aug 22, 2026
CVE Published
via MITRE·12:26 PM
Data Sourced
via MITRE·12:26 PM
DescriptionWeakness
Data Sourced
via NVD·01:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Deployments using the Netty io.netty:netty-codec-socks client encoders are affected if they run versions 4.2.0.Final through 4.2.16.Final, or 4.1.x through 4.1.136.Final. The affected components are Socks4ClientEncoder and Socks5ClientEncoder.

2

What must an attacker control to exploit it?

An attacker must be able to control SOCKS destination domain fields or authentication username/password fields processed by the affected client encoders. Null-byte or CRLF characters in those fields can truncate or alter encoded values and cause protocol confusion or credential injection.

3

How can I remediate the issue?

Upgrade to Netty 4.2.17.Final or 4.1.137.Final. These releases fix validation of the affected SOCKS domain and authentication fields.

4

What can be done while an upgrade is pending?

Do not pass attacker-controlled values directly into SOCKS domain, username, or password fields. Validate or reject null-byte and CRLF characters in these inputs before they reach Socks4ClientEncoder or Socks5ClientEncoder.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203