BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-45536High confidence

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

netty · netty

Official source article: GitHub GHSA-W573-9FFJ-6FF9 ↗. Check the applicable product and release in the original source.

4.0MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 42 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.19% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs netty netty and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 42 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcenettyAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcenettyAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcenettyAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcenettyAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appsnettyUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges8 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenio.netty:netty-transport-native-epollECOSYSTEM: introduced 4.2.0.Final; fixed 4.2.15.Final4.2.15.FinalOSV record ↗aggregator derived · 10 Sep 2026
Mavenio.netty:netty-transport-native-epollECOSYSTEM: introduced 0; fixed 4.1.135.Final4.1.135.FinalOSV record ↗aggregator derived · 10 Sep 2026
Mavenio.netty:netty-transport-native-kqueueECOSYSTEM: introduced 4.2.0.Final; fixed 4.2.15.Final4.2.15.FinalOSV record ↗aggregator derived · 10 Sep 2026
Mavenio.netty:netty-transport-native-kqueueECOSYSTEM: introduced 0; fixed 4.1.135.Final4.1.135.FinalOSV record ↗aggregator derived · 10 Sep 2026
mavenio.netty:netty-transport-native-epoll>= 4.2.0.Final, <= 4.2.14.Final4.2.15.FinalGitHub advisory ↗upstream repository advisory · 12 Jun 2026
mavenio.netty:netty-transport-native-epoll<= 4.1.134.Final4.1.135.FinalGitHub advisory ↗upstream repository advisory · 12 Jun 2026
mavenio.netty:netty-transport-native-kqueue>= 4.2.0.Final, <= 4.2.14.Final4.2.15.FinalGitHub advisory ↗upstream repository advisory · 12 Jun 2026
mavenio.netty:netty-transport-native-kqueue<= 4.1.134.Final4.1.135.FinalGitHub advisory ↗upstream repository advisory · 12 Jun 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-45536 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynetty-transport-native-epoll: netty-transport-native-kqueue: Netty: Denial of Service due to file descriptor leak in SCM_RIGHTS message handling
38 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • netty-transport-native-epoll as a component of Cryostat 4
  • netty-transport-native-epoll as a component of Red Hat AMQ Broker 7
  • netty-transport-native-kqueue as a component of Red Hat AMQ Broker 7
  • netty-transport-native-epoll as a component of Red Hat AMQ Clients
  • netty-transport-native-kqueue as a component of Red Hat AMQ Clients
  • netty-transport-native-epoll as a component of Red Hat build of Apache Camel - HawtIO 4
  • netty-transport-native-epoll as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • netty-transport-native-kqueue as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • netty-transport-native-epoll as a component of Red Hat build of Apache Camel for Spring Boot 4
  • netty-transport-native-kqueue as a component of Red Hat build of Apache Camel for Spring Boot 4
  • netty-transport-native-epoll as a component of Red Hat build of Debezium 3
  • netty-transport-native-kqueue as a component of Red Hat build of Debezium 3
Summary
A flaw was found in Netty, a network application framework. A local attacker could exploit a vulnerability in the `netty_unix_socket_recvFd` function when handling `SCM_RIGHTS` messages in `Epoll` or `KQueue DomainSocketChannel` with `DomainSocketReadMode.FILE_DESCRIPTORS` enabled. Incorrect handling of file descriptors could lead to a resource leak, resulting in a Denial of Service (DoS) due to exhaustion of available file descriptors.
Remediation
To mitigate this issue, ensure that `DomainSocketReadMode.FILE_DESCRIPTORS` is not enabled in applications utilizing Netty's `Epoll` or `KQueue DomainSocketChannel`. This feature is not enabled by default, and disabling it prevents the file descriptor leak that could lead to a Denial of Service.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-36439

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 42 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Exposure of Sensitive Information to an Unauthorized Actor → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-200 ↗

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedCWE-200
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-1814Netty: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Netty ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand herbeizuführen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1206Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2026-44249 Référence CVE CVE-2026-44250 https://www.cve.org/CVERecord?id=CVE-2026-44250 Référence CVE CVE-2026-44431 https://www.cve.org/CVERecord?id=CVE-2026-44431 Référence CVE CVE-2026-44432 https://www.cve.org/CVERecord?id=CVE-2026-44432 Référence CVE CVE-2026-44890 https://www.cve.org/CVERecord?id=CVE-2026-44890 Référence CVE CVE-2026-44893 https://www.cve.org/CVERecord?id=CVE-2026-44893 Référence CVE CVE-2026-45205 https://www.cve.org/CVERecord?id=CVE-2026-45205 Référence CVE CVE-2026-4539 https://www.cve.org/CVERecord?id=CVE-2026-4539 Référence CVE CVE-2026-45416 https://www.cve.org/CVERecord?id=CVE-2026-45416 Référence CVE CVE-2026-45536 https://www.cve.org/CVERecord?id=CVE-2026-45536 Référence CVE CVE-2026-46917 https://www.cve.org/CVERecord?id=CVE-2026-46917 Référence CVE CVE-2026-46968 https://www.cve.org/CVERecord?id=CVE-2026-46968 Référence CVE CVE-2026-47010 https://www.cve.org/CVERecord?id=CVE-2026-47010 Référence CVE CVE-2026-47021 https://www.cve.org/CVERecord?id=CVE-2026-47021 Référence CVE CVE-2026-47027 https://www.cve.org/CVERecord?id=CVE-2026-47027 Référence CVE CVE-2026-47057 https://www.cve.org/CVERecord?id=CVE-2026-47057 Référence CVE CVE-2026-47058 https://www.cve.org/CVERecord?id=CVE-2026-47058 Référence CVE CVE-2026-47059 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-019797Nettyにおける複数の脆弱性

Nettyはプロトコルサーバーおよびクライアントの開発のためのネットワークアプリケーションフレームワークです。バージョン4.1.135.Finalおよび4.2.15.Final以前のnetty_unix_socket_recvFdは、msg_controlを`char control[CMSG_SPACE(sizeof(int))]`（940行目）に設定しています。これは64ビットLinuxで24バイトです。ピアから送信されたSCM_RIGHTSのcmsgは2つのintを運び、cmsg_len = CMSG_LEN(8) = 24となります。MSG_CTRUNCなしでちょうど収まるため、カーネルは受信プロセスに両方のfdをインストールします。続く`cmsg-cmsg_len == CMSG_LEN(sizeof(int))`（972行目、期待値20）のチェックは失敗し、fdを読み取る分岐がスキップされます。そのため、インストールされたfdはいずれもクローズされません。for(;;)ループは再びrecvmsgを呼び出し（ノンブロッキング→EAGAIN→Javaでは0にマッピング→読み取りループは正常に終了します）、結果としてメッセージごとに2つのfdがリークします。MSG_CTRUNCの処理は実装されていません。アプリケーションがDomainSocketReadMode.FILE_DESCRIPTORS（デフォルトではありません）を選択した場合、Epoll/KQueue DomainSocketChannel経由でこの問題に到達可能です。バージョン4.1.135.Finalおよび4.2.15.Finalでこの問題は修正されています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
To mitigate this issue, ensure that `DomainSocketReadMode.FILE_DESCRIPTORS` is not enabled in applications utilizing Netty's `Epoll` or `KQueue DomainSocketChannel`. This feature is not enabled by default, and disabling it prevents the file descriptor leak that could lead to a Denial of Service.
04

Evidence and provenance

Published 12 Jun 2026 · Last source change 12 Jun 2026, 15:05 UTC · CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-36439
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-45536 to remediation: access.redhat.com/CVE-2026-45536.
    Before
    remediation: access.redhat.com/CVE-2026-45536
    After
    remediation: access.redhat.com/CVE-2026-45536
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Patch available to Mitigation available.
    Before
    Patch available
    After
    Mitigation available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    netty-transport-native-epoll as a component of Cryostat 4; netty-transport-native-epoll as a component of Red Hat AMQ Broker 7; netty-transport-native-kqueue as a component of Red Hat AMQ Broker 7; netty-transport-native-epoll as a component of Red Hat AMQ Clients; netty-transport-native-kqueue as a component of Red Hat AMQ Clients; netty-transport-native-epoll as a component of Red Hat build of Apache Camel - HawtIO 4; netty-transport-native-epoll as a component of Red Hat build of Apache Camel 4 for Quarkus 3; netty-transport-native-kqueue as a component of Red Hat build of Apache Camel 4 for Quarkus 3; netty-transport-native-epoll as a component of Red Hat build of Apache Camel for Spring Boot 4; netty-transport-native-kqueue as a component of Red Hat build of Apache Camel for Spring Boot 4; netty-transport-native-epoll as a component of Red Hat build of Debezium 3; netty-transport-native-kqueue as a component of Red Hat build of Debezium 3; netty-transport-native-epoll as a component of Red Hat Build of Keycloak; rhbk-openshift-rhel9/rhbk-openshift-rhel9 as a component of Red Hat Build of Keycloak; rhbk/keycloak-rhel9 as a component of Red Hat Build of Keycloak; netty-transport-native-epoll as a component of Red Hat Data Grid 8; netty-transport-native-kqueue as a component of Red Hat Data Grid 8; netty-transport-native-epoll as a component of Red Hat Fuse 7; netty-transport-native-kqueue as a component of Red Hat Fuse 7; netty-transport-native-epoll as a component of Red Hat JBoss Enterprise Application Platform 7; netty-transport-native-epoll as a component of Red Hat JBoss Enterprise Application Platform 8; netty-transport-native-epoll as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; netty-transport-native-kqueue as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; offline-knowledge-portal/rhokp-rhel9 as a component of Red Hat Offline Knowledge Portal; rhoai/odh-modelmesh-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-openvino-model-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-spark-operator-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cpu-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cpu-torch291-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cuda130-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); and 8 more · Fixed: Red Hat JBoss Enterprise Application Platform 8.1
    After
    netty-transport-native-epoll as a component of Cryostat 4; netty-transport-native-epoll as a component of Red Hat AMQ Broker 7; netty-transport-native-kqueue as a component of Red Hat AMQ Broker 7; netty-transport-native-epoll as a component of Red Hat AMQ Clients; netty-transport-native-kqueue as a component of Red Hat AMQ Clients; netty-transport-native-epoll as a component of Red Hat build of Apache Camel - HawtIO 4; netty-transport-native-epoll as a component of Red Hat build of Apache Camel 4 for Quarkus 3; netty-transport-native-kqueue as a component of Red Hat build of Apache Camel 4 for Quarkus 3; netty-transport-native-epoll as a component of Red Hat build of Apache Camel for Spring Boot 4; netty-transport-native-kqueue as a component of Red Hat build of Apache Camel for Spring Boot 4; netty-transport-native-epoll as a component of Red Hat build of Debezium 3; netty-transport-native-kqueue as a component of Red Hat build of Debezium 3; netty-transport-native-epoll as a component of Red Hat Build of Keycloak; rhbk-openshift-rhel9/rhbk-openshift-rhel9 as a component of Red Hat Build of Keycloak; rhbk/keycloak-rhel9 as a component of Red Hat Build of Keycloak; netty-transport-native-epoll as a component of Red Hat Data Grid 8; netty-transport-native-kqueue as a component of Red Hat Data Grid 8; netty-transport-native-epoll as a component of Red Hat Fuse 7; netty-transport-native-kqueue as a component of Red Hat Fuse 7; netty-transport-native-epoll as a component of Red Hat JBoss Enterprise Application Platform 7; netty-transport-native-epoll as a component of Red Hat JBoss Enterprise Application Platform 8; netty-transport-native-epoll as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; netty-transport-native-kqueue as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; offline-knowledge-portal/rhokp-rhel9 as a component of Red Hat Offline Knowledge Portal; rhoai/odh-modelmesh-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-openvino-model-server-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-spark-operator-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cpu-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cpu-torch291-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); rhoai/odh-th06-cuda130-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI); and 8 more
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    >= 4.2.0.Final, < 4.2.15.Final; < 4.1.135.Final · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    >= 4.2.0.Final, < 4.2.15.Final; < 4.1.135.Final · Fixed: Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  5. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-36439↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-W573-9FFJ-6FF9↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-45536 · cve.blacktree.nl