Security Resilience

CVE-2026-73507

DoS in Netty ≤ 4.1.136

Published
13 August 2026
Modified
23 September 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0079 56th percentile
Risk Priority 59 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-73507 is a high-severity Uncontrolled Resource Consumption (CWE-400) vulnerability in Netty. Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-5 (Denial-of-service Protection) and SC-6 (Resource Availability) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Netty is an asynchronous, event-driven network application framework. Prior to 4.1.136.Final and 4.2.16.Final, io.netty.handler.codec.xml.XmlFrameDecoder.decode() failed to preserve closing-tag parser state across invocations, so an unauthenticated remote attacker could trickle-feed repeated </ sequences that repeatedly rescanned the accumulated buffer and exhausted…

more

an EventLoop thread's CPU, causing denial of service with a maxFrameLength of 1 MB. This issue is fixed in versions 4.1.136.Final and 4.2.16.Final.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-59902Same product: Netty Netty
CVE-2026-55833Same product: Netty Netty
CVE-2026-55851Same product: Netty Netty
CVE-2026-47244Same product: Netty Netty
CVE-2026-56745Same product: Netty Netty
CVE-2026-56816Same product: Netty Netty
CVE-2026-44892Same product: Netty Netty
CVE-2026-42587Same product: Netty Netty
CVE-2026-44250Same product: Netty Netty
CVE-2023-34462Same product: Netty Netty

Affected Assets

netty
netty
≤ 4.1.136 · 4.2.0 — 4.2.16

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

SC-5 directly limits the effects of resource-exhaustion events that constitute uncontrolled consumption.

SC-6 enforces explicit allocation limits on resources, structurally preventing the weakness from occurring.

Process isolation confines resource consumption to separate domains, reducing blast radius without stopping the root flaw.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Resource-utilization monitoring and alerting on bottlenecks or overloads limits the impact of denial-of-service or resource-exhaustion attacks.

finds

Early notification of anomalous resource consumption or system malfunctions enables throttling or isolation before availability is lost.

blocks

Monitoring network service usage and applying controls to restrict access when necessary limits an attacker’s ability to consume excessive resources through unrestricted or unauthenticated service calls.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-400, a class-level weakness. Rules are authored against its narrower children: CWE-770.

References