Improper Verification of Cryptographic Signature Affecting eap7-netty package, versions <0:4.1.135-1.Final_redhat_00001.1.el7eap


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.46% (38th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-EAP7NETTY-18682427
  • published12 Aug 2026
  • disclosed12 Jun 2026

Introduced: 12 Jun 2026

CVE-2026-50010  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

Upgrade RHEL:7 eap7-netty to version 0:4.1.135-1.Final_redhat_00001.1.el7eap or higher.
This issue was patched in RHSA-2026:53644.

NVD Description

Note: Versions mentioned in the description apply only to the upstream eap7-netty package and not the eap7-netty package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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, SimpleTrustManagerFactory.engineGetTrustManagers() and related paths wrap any user-supplied plain X509TrustManager in X509TrustManagerWrapper, which extends X509ExtendedTrustManager but implements the 3-arg checkServerTrusted(chain, authType, SSLEngine) by discarding the SSLEngine and calling the 2-arg delegate. Because the object now IS an X509ExtendedTrustManager, neither SunJSSE's internal AbstractTrustManagerWrapper nor Netty's own OpenSslX509TrustManagerWrapper will re-wrap it to add endpoint-identification. Consequently, even though Netty 4.2 sets endpointIdentificationAlgorithm="HTTPS" by default, a client built with SslContextBuilder.forClient().trustManager(somePlainX509TrustManager) performs no hostname verification at all. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

CVSS Base Scores

version 3.1