CVE-2026-62380
Description
A flaw was found in the Netty SOCKS client encoders. This vulnerability allows a remote attacker to inject null bytes or Carriage Return Line Feed (CRLF) characters into domain address and authentication fields due to insufficient validation. By manipulating these fields, an attacker can truncate or alter values, potentially leading to domain spoofing, SOCKS4 user ID truncation, authentication data injection, and protocol confusion.
Statement
A MODERATE severity flaw was found in the Netty SOCKS client encoders (Socks4ClientEncoder and Socks5ClientEncoder in io.netty:netty-codec-socks), a component shipped across numerous Red Hat products and offerings, including Red Hat JBoss Fuse, Red Hat Single Sign-On, Red Hat Integration, Red Hat Enterprise Linux AI, Red Hat OpenShift Dev Spaces, and cloud.redhat.com services. The encoders do not properly validate domain address and authentication (username/password) fields. A remote attacker able to control these fields can inject null bytes or CRLF characters to truncate or alter the encoded values, potentially leading to domain spoofing, SOCKS4 user ID truncation, authentication data injection, and SOCKS protocol confusion. The consequence is limited to data integrity; there is no direct impact on confidentiality or availability. Red Hat's severity rating (MODERATE, CVSS 5.3) differs from the NIST score (IMPORTANT, CVSS 7.5) because Red Hat assessed that exploitation requires attacker control of client-supplied SOCKS fields and results in only low integrity impact, whereas NIST scored the integrity impact as high. For a number of affected product streams the fix is currently deferred, so those releases continue to ship the vulnerable encoders and the residual risk of SOCKS field manipulation persists until an updated Netty version is incorporated; the Fedora community affect is delegated, with the fix pursued by the Fedora project.
Mitigation
Applications utilizing Netty's SOCKS client encoders should implement robust input validation and sanitization for all domain address and authentication credential fields. If SOCKS proxy client functionality is not required by the application, it should be disabled to remove the attack surface.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.3 | 7.5 | N/A |
| Attack Vector | Network | Network | N/A |
| Attack Complexity | Low | Low | N/A |
| Privileges Required | None | None | N/A |
| User Interaction | None | None | N/A |
| Scope | Unchanged | Unchanged | N/A |
| Confidentiality | None | None | N/A |
| Integrity Impact | Low | High | N/A |
| Availability Impact | None | None | N/A |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Application Data
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
