Skip to content

← Public intelligence

Maven package

io.netty:netty-codec-stomp

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5MavenPublished

    Netty: STOMP CONNECT Frame Header Injection in Netty

    CVE-2026-59920 · GHSA-3g8r-4pfx-jmfh

    Affected
    • Maven io.netty:netty-codec-stomp >= 4.2.0.Final, < 4.2.16.Final; < 4.1.136.Final
    Fixed in
    4.2.16.Final4.1.136.Final· Vendor fix available
    Issue
    Security Vulnerability Report: STOMP CONNECT Frame Header Injection in Netty 1. Vulnerability Summary | Field | Value | |-------|-------| | Product | Netty | | Version | 4.2.12.Final (and all prior versions with codec-stomp) | | Component | io.netty.handler.codec.stomp.StompSubframeEncoder | | Vulnerability Type | CWE-93: Improper Neutralization of CRLF Sequences / CWE-113: Improper Neutralization of CRLF in HTTP Headers | | Impact | STOMP Header Injection / Authentication Bypass | | CVSS 3.1 Score | 6.5 (Medium) | | CVSS 3.1 Vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N | | Attack Vector | Network | | Attack Complexity | Low | | Privileges Required | Low | | User Interaction | None | | Scope | Unchanged | | Confidentiality Impact | None | | Integrity Impact | High | | Availability Impact | None | 2. Affected Components - io.netty.handler.codec.stomp.StompSubframeEncoder — encodeHeaders() method (lines 174-200) - io.netty.handler.codec.stomp.StompSubframeEncoder —…

    Recommended action: Upgrade to 4.2.16.Final or 4.1.136.Final by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5MavenPublished

    Netty: Denial of Service via Unbounded Headers in StompSubframeDecoder

    CVE-2026-44891 · GHSA-vhch-2wf3-m8rp

    Affected
    • Maven io.netty:netty-codec-stomp >= 4.2.0.Alpha1, <= 4.2.15.Final; <= 4.1.135.Final
    Fixed in
    4.2.16.Final4.1.136.Final· Vendor fix available
    Issue
    The StompSubframeDecoder fails to limit the total number of headers or their cumulative size per frame, allowing an attacker to cause an OutOfMemoryError, leading to a Denial of Service. Details io.netty.handler.codec.stomp.StompSubframeDecoder implements the STOMP protocol. The maxLineLength parameter restricts the length of individual header lines, but there is no mechanism to limit the total number of headers in a single STOMP frame. An attacker can send a large number of short headers (e.g., a: 1\n), which are accumulated in memory inside the DefaultStompHeadersSubframe until the JVM throws an OutOfMemoryError. PoC Run the server with -Xmx256m Impact Denial of Service: An attacker can easily exhaust the server's memory by sending a single malicious STOMP message. Any server exposing a STOMP endpoint based on StompSubframeDecoder is vulnerable to DoS.

    Recommended action: Upgrade to 4.2.16.Final or 4.1.136.Final by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →