CVE-2026-45536

Netty: Unix-socket fd receive leaks descriptors when peer sends two at once

MEDIUM
4
CVSS Score
Published: June 12, 2026 at 02:12 PM UTC
Updated: June 17, 2026 at 10:52 AM UTC
1 product affected across 1 vendorNetty

Using netty by netty?

Get instant alerts when new vulnerabilities affect netty - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, netty_unix_socket_recvFd sets msg_control to `char control[CMSG_SPACE(sizeof(int))]` (line 940) — 24 bytes on 64-bit Linux. A peer-sent SCM_RIGHTS cmsg carrying two ints has cmsg_len = CMSG_LEN(8) = 24, which fits exactly with no MSG_CTRUNC, so the kernel installs both fds in the receiving process. The subsequent check `cmsg->cmsg_len == CMSG_LEN(sizeof(int))` (line 972, expected 20) fails, the branch that would read the fd is skipped, and neither installed fd is closed. The for(;;) loop calls recvmsg again (non-blocking → EAGAIN → Java maps to 0 → read loop exits normally), leaving two leaked fds per message. There is no MSG_CTRUNC handling. Reachable via Epoll/KQueue DomainSocketChannel when the application opts into DomainSocketReadMode.FILE_DESCRIPTORS (non-default). Versions 4.1.135.Final and 4.2.15.Final patch the issue.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 4.1.135v < 4.1.135.Finalv < 4.2.15.Final4.2.0 ≤ v < 4.2.15
Affected range stops below 4.1.135, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.135.Final, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.2.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.2.15.Final, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

x_refsource_CONFIRMVendor Advisory
Source: cverecord
https://github.com/netty/netty/security/advisories/GHSA-w573-9ffj-6ff9
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/netty/netty/releases/tag/netty-4.1.135.Final
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/netty/netty/releases/tag/netty-4.2.15.Final

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4MEDIUMGitHub_M
Attack Vector
LOCAL
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusANALYZED
CWE
CWE-200CWE-772

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card