Loading vulnerability…
CVE-2026-5295 is a stack-based buffer overflow in wolfSSL's PKCS7 implementation, specifically in wc_PKCS7_DecryptOri() in wolfcrypt/src/pkcs7.c. When processing a CMS/PKCS7 EnvelopedData message containing an OtherRecipientInfo (ORI) recipient, the function copies an ASN.1-parsed object identifier into a fixed-size 32-byte stack buffer, oriOID[MAX_OID_SZ], using XMEMCPY without validating that the parsed OID length is at most MAX_OID_SZ. A crafted CMS EnvelopedData / PKCS7 envelope containing an ORI recipient with an OID longer than 32 bytes can therefore overflow the stack buffer during parsing/decryption. The issue affects configurations where PKCS7 support is enabled and ORI handling is used.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.