{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-62380 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-62380 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2026-62380 in the wild and no public exploit code.\n\nAffected product: Netty Netty. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-62380/ (Markdown: https://insights.sbomify.com/CVE-2026-62380/index.md)","id":"CVE-2026-62380","markdown":"https://insights.sbomify.com/CVE-2026-62380/index.md","name":"CVE-2026-62380","record":{"aliases":["CLEANSTART-2026-BC54924","CLEANSTART-2026-NB43165","CLEANSTART-2026-PK97624","CLEANSTART-2026-VB05004","CLEANSTART-2026-VD69518","CLEANSTART-2026-YC22300","DEBIAN-CVE-2026-62380","GHSA-cc6x-ffm5-83wf","GHSA-jmpc-xv4r-m7fw","UBUNTU-CVE-2026-62380"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Netty SOCKS codec","requires_auth":"none","summary":"Attackers can inject null bytes or CRLF into SOCKS proxy fields to spoof domains or alter authentication data in Netty applications.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"netty","vendor":"netty"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-626","name":"Null Byte Interaction Error (Poison Null Byte)"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Netty before 4.2.16.Final SOCKS Proxy Null Byte Injection","id":"CVE-2026-62380","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"netty:netty","products":["netty:netty"],"type":"other","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"luci-lib-px5g 2040-bit Certificate Signing Heap Buffer Overflow","id":"CVE-2026-62381"},"packages":[],"prev":{"headline":"OpenAM: Unauthenticated Remote Code Execution via Class.forName in AuthXMLUtils.createCustomCallback","id":"CVE-2026-62379"},"products":["netty"],"published":"2026-08-22","related":[{"cvss_score":9.1,"headline":"Netty: SNI Routing Bypass via Fragmented TLS ClientHello Causing Fallback to Default SslContext","id":"CVE-2026-75595","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":8.7,"headline":"Netty: Fragmented ClientHello records trigger quadratic pre-handshake reassembly in default SNI parsing","id":"CVE-2026-75596","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":8.7,"headline":"Netty Bzip2Decoder: Infinite Loop in RLE State Machine Leads to Event-Loop Thread Hang","id":"CVE-2026-59901","kev_date_added":null,"published":"2026-07-29"},{"cvss_score":8.7,"headline":"Netty codec-haproxy: Signed-Byte Sentinel Collision in HAProxyMessageDecoder Leads to Unbounded Memory Exhaustion","id":"CVE-2026-55851","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":8.7,"headline":"Netty SpdyHttpDecoder: ByteBuf Reference Leak on RST_STREAM Leads to Native Memory Exhaustion","id":"CVE-2026-56745","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":8.7,"headline":"Netty Vulnerable to DNS Cache Poisoning via Missing Bailiwick Checks in CNAME Records","id":"CVE-2026-45674","kev_date_added":null,"published":"2026-06-12"},{"cvss_score":8.7,"headline":"Netty has Insufficient Bailiwick Validation for NS Records","id":"CVE-2026-47691","kev_date_added":null,"published":"2026-06-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-26","vendors":["netty"]},"summary":"Attackers can inject null bytes or CRLF into SOCKS proxy fields to spoof domains or alter authentication data in Netty applications.","url":"https://insights.sbomify.com/CVE-2026-62380/"}