Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-w573-9ffj-6ff9

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

CVSS 4.0 MediumEPSS 0.0014 · 3rd percentile

Published by the GitHub Advisory Database at 8 Jun 2026, 23:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.netty:netty-transport-native-epollMaven>=4.2.0.Final, <4.2.15.Final || <4.1.135.Final4.2.15.Final, 4.1.135.Final
io.netty:netty-transport-native-kqueueMaven>=4.2.0.Final, <4.2.15.Final || <4.1.135.Final4.2.15.Final, 4.1.135.Final
Identifiers
GHSA-w573-9ffj-6ff9 · CVE-2026-45536
Weakness (CWE)
CWE-200 · CWE-772
Tags
Published
8 Jun 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Netty's netty-transport-native-epoll and netty-transport-native-kqueue packages, versions 4.2.0.Final up to but not including 4.2.15.Final, and 4.1.x versions before 4.1.135.Final, are affected. A peer that sends two file descriptors in one Unix-domain socket message can cause the receiver to leak both descriptors, one pair per message. This occurs only when the application enables DomainSocketReadMode.FILE_DESCRIPTORS, which is not the default. Upgrade to 4.2.15.Final or 4.1.135.Final, or later.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.0 Medium 3.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0014, the 3rd percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.