Loading vulnerability…
wolfSSL contains a heap use-after-free in TLS 1.3 post-quantum cryptography hybrid KeyShare processing. In the error-handling path of TLSX_KeyShare_ProcessPqcHybridClient() in src/tls.c, the inner routine TLSX_KeyShare_ProcessPqcClient_ex() frees a KyberKey object when parsing fails. The caller subsequently invokes TLSX_KeyShare_FreeAll(), which attempts to ForceZero() and free the same KyberKey again. This results in zeroing and cleanup operations being performed on already-freed heap memory. The issue is triggered when a malicious TLS 1.3 server sends a malformed or truncated PQC hybrid KeyShare in ServerHello, such as an undersized P256_ML_KEM_512 key share.
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.
5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.