CVE-2026-50010 is an improper certificate-validation flaw in Netty's netty-handler TLS trust-manager handling. Netty wrapped a caller-supplied plain X509TrustManager in an X509ExtendedTrustManager-compatible wrapper whose SSLEngine-aware server-certificate validation method discarded the SSLEngine and delegated to the two-argument method. This prevented the JDK or Netty provider wrappers from adding endpoint-identification behavior. Consequently, a TLS client configured with a plain custom trust manager could accept a certificate valid for a trusted CA but issued for a different hostname, despite HTTPS endpoint identification being configured by default in Netty 4.2. An additional affected OpenSSL-provider condition exists on Java 25 and later: when Unsafe-based reflective wrapping is unavailable, a plain non-extended trust manager can remain unwrapped and hostname verification is not applied.
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.
46 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Netty handler vulnerability that allows hostname verification bypass due to improper trust manager handling.
A Netty handler vulnerability that allows hostname verification bypass due to improper trust manager handling.
A Netty handler vulnerability where improper trust manager handling can lead to TLS hostname verification bypass.
A Netty vulnerability where improper trust manager handling can lead to hostname verification bypass.
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.