Loading vulnerability…
CVE-2026-50010 is an improper certificate validation vulnerability in Netty's netty-handler module affecting versions prior to 4.1.135.Final and 4.2.15.Final. The flaw is in SimpleTrustManagerFactory.engineGetTrustManagers() and related trust-manager wrapping paths, where a user-supplied legacy X509TrustManager is wrapped in X509TrustManagerWrapper, which extends X509ExtendedTrustManager. In the connection-aware checkServerTrusted methods, the wrapper discards the Socket or SSLEngine context and delegates only to the legacy two-argument checkServerTrusted(chain, authType) method. Because the wrapped object now appears to be an X509ExtendedTrustManager, neither JSSE nor Netty's OpenSSL trust-manager adaptation layers apply additional endpoint-identification logic. As a result, client TLS connections built with a user-supplied plain X509TrustManager can validate the certificate chain without verifying that the certificate matches the intended hostname. This causes hostname verification to be silently skipped even when HTTPS endpoint identification is expected to be enabled.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A hostname verification bypass in Netty's trust manager wrapping logic where a wrapped legacy X509TrustManager is treated as X509ExtendedTrustManager, causing connection-aware endpoint identification to be skipped and allowing acceptance of valid certificates for the wrong domain.
A Netty TLS certificate validation flaw where hostname verification is not performed with a user-supplied plain X509TrustManager, enabling disclosure of sensitive information.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.