A flaw was found in Netty's StompSubframeDecoder component. A remote attacker can exploit this vulnerability by sending a specially crafted STOMP frame body without its terminating null byte. This causes the decoder to allocate a ByteBuf (a buffer for bytes) that is never released, leading to a permanent memory leak. Over time, this uncontrolled memory consumption can result in a Denial of Service (DoS) for the application using the affected STOMP codec.
CVE-2026-93494
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-18. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (1)
Auto-updated Sep 18, 20262536898 – (CVE-2026-93494) CVE-2026-93494 netty: netty-codec-stomp: io.netty/netty-codec-stomp: Netty: ByteBuf Leak in StompSubframeDecoder When a Frame Body Is Never Terminated
https://bugzilla.redhat.com/show_bug.cgi?id=2536898Vendor Advisories for CVE-2026-93494(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:08 UTCEG score recompute
- 2026-09-18 19:08 UTCGHSA enrichment
- 2026-09-18 11:19 UTCGHSA enrichment
- 2026-09-18 10:49 UTCEG score recompute▲ 7.50
- 2026-09-18 10:49 UTCGHSA enrichment
- 2026-09-18 10:49 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-09-18 08:26 UTCNVD update
- 2026-09-18 07:49 UTCEG score recompute
- 2026-09-18 07:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-93494?
When was CVE-2026-93494 disclosed?
What is the CVSS score of CVE-2026-93494?
How do I remediate CVE-2026-93494?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93494
Is Your Infrastructure Affected by CVE-2026-93494?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.