Loading vulnerability…
CVE-2026-89133 is an improper X.509 certificate validation vulnerability in wolfSSL 5.9.2 and earlier. The certificate-chain validation state machine fails to preserve NameConstraints enforcement when it encounters an unconstrained CA between a name-constrained intermediate CA and the leaf certificate. As a result, wolfSSL can accept a certificate for a hostname outside the DNS namespace authorized by the constrained CA.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Medium-severity X.509 DNS name-constraint validation bypass in wolfSSL certificate-chain handling.
Medium-severity wolfSSL X.509 DNS NameConstraints validation bypass involving an unconstrained CA between a constrained intermediate CA and leaf certificate.
A certificate-validation bypass in wolfSSL 5.9.2 and earlier. A chain-walking state-machine flaw resets NameConstraints validation upon encountering an unconstrained intermediate CA, allowing certificates to be accepted for unauthorized hostnames and bypassing cryptographic delegation restrictions.
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.