CVE-2026-81701 affects openssl_encrypt versions earlier than 1.4.9. The plugin trust mechanism uses a denylist to identify built-in trusted plugins rather than requiring verification for all non-trusted plugins. Consequently, unsigned plugins located directly in top-level plugin directories or within unrecognized subdirectories can bypass signature verification. A malicious plugin placed through a documented plugin installation location may be loaded and executed by the openssl_encrypt CLI process.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A signature-verification bypass in openssl_encrypt prior to version 1.4.9. Its denylist-based identification of trusted built-in plugins permits malicious unsigned plugins placed in documented plugin paths to execute arbitrary code in the CLI process, potentially exposing passwords and cryptographic keys.
An arbitrary-code-execution vulnerability in openssl_encrypt versions before 1.4.9. Its plugin trust-validation logic uses a denylist, allowing unsigned plugins installed in documented top-level or unknown plugin subdirectories to bypass signature verification and execute in the CLI process, potentially exposing passwords and cryptographic keys.
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.