Netty is a network application framework for development of protocol servers and clients. In versions of netty-transport-sctp prior to 4.1.135.Final and 4.2.15.Final, for each non-complete SctpMessage fragment the handler does fragments.put(streamId, Unpooled.wrappedBuffer(frag, byteBuf)), wrapping the previous accumulator and the new slice into a *new* CompositeByteBuf every time. After N fragments the accumulator is an N-deep chain of composites, each holding references and component arrays; readableBytes()/getBytes() on the final buffer recurse N levels. There is no limit on N, on total bytes, or on the number of streamIdentifiers an attacker can open (each gets its own map entry). A peer that never sets the complete flag can grow this structure indefinitely from tiny 1-byte DATA chunks. Versions 4.1.135.Final and 4.2.15.Final patch the issue.
CVE-2026-46340
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 54% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/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%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 46%
- KEV
- Not listed
Published
June 8, 2026
Last Modified
August 12, 2026
Advisory Details (3)
Auto-updated Jun 12, 2026SCTP reassembly nests buffers without bound · Advisory · netty/netty · GitHub
https://github.com/netty/netty/security/advisories/GHSA-5xrh-qmmq-w6chnetty-4.2.15.Final
Patch available: netty/netty netty-4.2.15.Final
https://github.com/netty/netty/releases/tag/netty-4.2.15.Finalnetty-4.1.135.Final
Patch available: netty/netty netty-4.1.135.Final
https://github.com/netty/netty/releases/tag/netty-4.1.135.FinalVendor Advisories for CVE-2026-46340(6)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:53806Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.25 security update
- RHSA-2026:53644Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.25 security pdate
- RHSA-2026:50085Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 8.1.7.1 XP 6.0.5.1 release
- RHSA-2026:41951Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Data Grid 8.6.2 security update
- RHSA-2026:37390Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Build of Apache Camel 4.18.1.P1 for Spring Boot release.
- GHSA-5xrh-qmmq-w6chGitHub Security AdvisoriesHigh
Netty: SCTP reassembly nests buffers without bound
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | netty-transport-sctp | 2026-08-11 | redhat |
| redhat | eap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el7eap | 2026-08-11 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| netty | 1:4.1.48-10 ... 1:4.1.48-9 (16 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| netty | 1:4.1.48-10 ... 1:4.1.48-9 (12 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| netty | 1:4.1.48-10 ... 1:4.1.48-16 (8 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| netty | 1:4.1.48-10 ... 1:4.1.48-16 (7 versions) | — | — |
Maven(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| io.netty:netty-transport-sctp | 4.0.0.Beta1 ... 4.1.99.Final (220 versions) | 4.1.135.Final | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 102× 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.
Showing the most recent 100 of 164 total refreshes for this CVE.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 01:13 UTCEG score recompute
- 2026-08-25 01:13 UTCVendor advisory
- 2026-08-23 23:46 UTCVendor advisory
- 2026-08-23 11:36 UTCEG score recompute
- 2026-08-23 11:36 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 19:52 UTCVendor advisory
- 2026-08-21 07:51 UTCEG score recompute
- 2026-08-21 07:51 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 20:54 UTCVendor advisory
- 2026-08-20 09:26 UTCEG score recompute
- 2026-08-20 09:26 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 12:39 UTCVendor advisory
- 2026-08-17 01:44 UTCEG score recompute
- 2026-08-17 01:44 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 11:54 UTCEG score recompute
- 2026-08-16 11:54 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-16 01:00 UTCVendor advisory
- 2026-08-15 11:45 UTCEG score recompute
- 2026-08-15 11:45 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 20:15 UTCVendor advisory
- 2026-08-14 09:21 UTCVendor advisory
- 2026-08-13 22:26 UTCEG score recompute
- 2026-08-13 22:26 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 10:25 UTCVendor advisory
- 2026-08-12 23:30 UTCEG score recompute
- 2026-08-12 23:30 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 12:36 UTCEG score recompute
- 2026-08-12 12:36 UTCVendor advisory
- 2026-08-12 12:11 UTCEG score recompute
- 2026-08-12 12:11 UTCVendor advisory
- 2026-08-12 10:40 UTCVendor advisory
- 2026-08-11 23:45 UTCEG score recompute
- 2026-08-11 23:45 UTCVendor advisory
- 2026-08-11 12:51 UTCVendor advisory
- 2026-08-11 01:41 UTCEG score recompute
- 2026-08-11 01:41 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 14:47 UTCVendor advisory
- 2026-08-10 03:52 UTCVendor advisory
- 2026-08-09 16:58 UTCEG score recompute
- 2026-08-09 16:58 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 06:04 UTCVendor advisory
- 2026-08-08 19:10 UTCEG score recompute
- 2026-08-08 19:10 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 08:15 UTCVendor advisory
- 2026-08-07 21:21 UTCEG score recompute
- 2026-08-07 21:21 UTCVendor advisory
- 2026-08-07 10:27 UTCVendor advisory
- 2026-08-06 23:33 UTCEG score recompute
- 2026-08-06 23:33 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 11:27 UTCVendor advisory
- 2026-08-06 00:33 UTCEG score recompute
- 2026-08-06 00:33 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 13:39 UTCEG score recompute
- 2026-08-05 13:39 UTCVendor advisory
- 2026-08-05 12:32 UTCEG score recompute
- 2026-08-05 12:32 UTCVendor advisory
- 2026-08-04 16:20 UTCEG score recompute
- 2026-08-04 16:20 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 02:14 UTCVendor advisory
- 2026-08-03 15:20 UTCEG score recompute
- 2026-08-03 15:20 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 19:31 UTCVendor advisory
- 2026-08-02 08:37 UTCEG score recompute
- 2026-08-02 08:37 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 21:43 UTCVendor advisory
- 2026-08-01 10:45 UTCEG score recompute
- 2026-08-01 10:45 UTCVendor advisory
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 16:15 UTCVendor advisory
- 2026-07-31 04:47 UTCEG score recompute
- 2026-07-31 04:47 UTCVendor advisory
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 17:09 UTCVendor advisory
- 2026-07-29 06:13 UTCEG score recompute
- 2026-07-29 06:13 UTCVendor advisory
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-28 02:51 UTCEG score recompute
- 2026-07-28 02:51 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-770
Frequently asked(5)
What is CVE-2026-46340?
When was CVE-2026-46340 disclosed?
Is CVE-2026-46340 actively exploited?
What is the CVSS score of CVE-2026-46340?
How do I remediate CVE-2026-46340?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46340
Is Your Infrastructure Affected by CVE-2026-46340?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.