Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-59920: Netty: STOMP CONNECT Frame Header Injection

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: io.netty:netty-codec-stomp (Maven) 4.2.16.Final, 4.1.136.Final; netty (openSUSE:Tumbleweed) 4.1.136-1.1; netty-tcnative (SUSE:Linux Enterprise Module for Development Tools 15 SP7) 2.0.80-150200.3.48.1.

Low priority for now. Upgrade to io.netty:netty-codec-stomp (Maven) 4.2.16.Final, 4.1.136.Final; netty (openSUSE:Tumbleweed) 4.1.136-1.1; netty-tcnative (SUSE:Linux Enterprise Module for Development Tools 15 SP7) 2.0.80-150200.3.48.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.5 · v3.1—No exploit Fix available
Published
Jul 29, 2026
Updated
Aug 6, 2026
EPSS
0.4% · 36th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
6.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-59920

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for netty records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
nettynetty

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • netty nettybefore 4.1.136
  • netty netty4.2.0 and later · before 4.2.16

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • netty netty

    • < 4.1.136.Final, >= 4.2.0.Final, < 4.2.16.Finalaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12nettyfrom 0—
Mavenio.netty:netty-codec-stompfrom 4.2.0.Final · before 4.2.16.Final4.2.16.Final
Mavenio.netty:netty-codec-stompbefore 4.1.136.Final4.1.136.Final
openSUSE:Tumbleweednettybefore 4.1.136-1.14.1.136-1.1
SUSE:Linux Enterprise Module for Development Tools 15 SP7netty-tcnativebefore 2.0.80-150200.3.48.12.0.80-150200.3.48.1
SUSE:Linux Enterprise Module for Package Hub 15 SP7nettybefore 4.1.136-150200.4.53.14.1.136-150200.4.53.1

Same product

netty: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-47691Netty has Insufficient Bailiwick Validation for NS Records
    40Plan
  • CVE-2026-45674Netty Vulnerable to DNS Cache Poisoning via Missing Bailiwick Checks in CNAME Records
    40Plan
  • CVE-2019-20445HttpObjectDecoder.java in Netty before 4.1.44 allows a Content-Length header to be accompanied by a second Content-Length header, or by a…
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-59901Jul 29, 2026 · Netty Bzip2Decoder: Infinite Loop in RLE State Machine Leads to Event-Loop Thread Hang
    34Monitor
  • ← EarlierCVE-2026-59919Jul 29, 2026 · Netty: HAProxy V1 Protocol CRLF Injection via AF_UNIX Address
    22Monitor
  • Later →CVE-2026-59898Jul 29, 2026 · Netty: WebSockets V07/V08 handshaker missing Connection/Upgrade validation
    25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:io.netty:netty-codec-stomp4.1.136.FinalPackage registry (OSV)
Maven:io.netty:netty-codec-stomp4.2.16.FinalPackage registry (OSV)
opensuse:netty4.1.136-1.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:netty4.1.136-150200.4.53.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7Package registry (OSV)
suse:netty-tcnative2.0.80-150200.3.48.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-4258677 days apartNetty: CRLF Injection in Netty Redis Codec Encoder
    28Monitor
  • CVE-2026-599211 days apartNetty: CRLF Injection via Multipart Filename in Netty HttpPostRequestEncoder
    26Monitor
  • CVE-2025-67735225 days apartNetty has a CRLF Injection vulnerability in io.netty.handler.codec.http.HttpRequestEncoder
    26Monitor
  • CVE-2026-599190 days apartNetty: HAProxy V1 Protocol CRLF Injection via AF_UNIX Address
    22Monitor
  • CVE-2025-59419287 days apartNetty netty-codec-smtp SMTP Command Injection Vulnerability Allowing Email Forgery
    22Monitor
  • CVE-2026-4141784 days apartNetty vulnerable to HTTP request smuggling and RTSP request injection via DefaultHttpRequest.setUri()
    21Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-93 · Improper Neutralization of CRLF Sequences ('CRLF Injection')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records