CVE-2026-50010

About vulnerability

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.

Affected product:

Apache CXF , Apache Hadoop , Apache Kafka , Apache Log4j , Apache Solr , Apache Spark , Eclipse Jetty , Netty , React , Spring , Wildfly , artemis , async-http-client , avro , aws-sdk-java , azure-sdk-for-java , bolt-connection-java , californium , camel , cassandra-java-driver , catalyst , couchbase-jvm-clients , curator , docker-java , drill , elasticsearch , flink , flink-shaded , grpc-java , infinispan , java-driver , lettuce , logging-flume , milo , neo4j-java-driver , neo4j-ogm , netty , olingo-odata4 , pgjdbc-ng , pulsar , rabbitmq-stream-java-client , rsocket-java , stack-core , tika , vert.x , wildfly , zendesk-java-client , zookeeper

Affected packages:

netty-handler @ 4.1.17.Final (+7577 more)

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.