Vulnerability in io.netty:netty-codec-stomp (CVE-2026-59920)
Summary
Vulnerability in io.netty:netty-codec-stomp (CVE-2026-59920). Data can be tampered with by attackers. Exploitable via StompSubframeEncoder. Mitigation: upgrade to 4.1.136.Final or later.
Original description
The description as published by the source.
Netty is an asynchronous, event-driven network application framework. In versions prior to 4.1.136.Final and 4.2.16.Final, Netty's STOMP encoder ( StompSubframeEncoder ) does not escape or validate header values in CONNECT and CONNECTED frames, so raw newline ( \n ) characters in a header value are written directly to the wire, allowing an attacker who controls a header value to inject additional STOMP headers. This happens because the encoder intentionally skips escaping for CONNECT/CONNECTED frames per the STOMP 1.2 specification but never rejects the raw newlines, and since a broker parses each line as a separate header, an attacker controlling a value such as a user-supplied login or passcode can overwrite connection parameters or add authentication/role headers to bypass authentication or escalate privileges (the actual impact is broker-dependent). The issue is fixed in versions 4.1.136.Final and 4.2.16.Final.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-59920 has been found in io.netty:netty-codec-stomp.
Attackers can target a specific entry point like StompSubframeEncoder over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade io.netty:netty-codec-stomp to 4.1.136.Final or later.
If unsure, ask your IT team or search "io.netty:netty-codec-stomp CVE-2026-59920" on the vendor's site.
CVE-2026-59920 (io.netty:netty-codec-stomp) — CWE-93 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: StompSubframeEncoder / CONNECT / CONNECTED / StompSubframeEncoder.java
Patched: 4.1.136.Final — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-93) exists in io.netty:netty-codec-stomp. Attackers reach the vulnerable code path via StompSubframeEncoder.
Check the vendor advisory for the affected versions of io.netty:netty-codec-stomp. Attack surface: StompSubframeEncoder / CONNECT / CONNECTED / StompSubframeEncoder.java.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 4.1.136.Final.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで io.netty:netty-codec-stomp を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade io.netty:netty-codec-stomp to 4.1.136.Finalステージング環境で 4.1.136.Final に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-59920 netty
- Ubuntu UBUNTU-CVE-2026-59920 netty
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com