CVE-2026-81714: critical vulnerability in jahlives openssl_encrypt
openssl_encrypt before 1.4.9 Plugin Signing Trust Anchor Enrollment Bypass
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.3epss 0.2%
openssl_encrypt (pip: openssl-encrypt) versions <= 1.4.8 use suffix-tolerant fingerprint matching in enroll_trust_key when binding a plugin-signing trust anchor. An operator who confirms a short (forgeable, ~32-bit) GPG key id could unknowingly enroll an attacker's colliding key as a trusted anchor, which then vouches for malicious plugins under the ENFORCE signature policy. Version 1.4.9 fixes this by requiring the confirmed value to exactly match the full primary-key fingerprint (case-insensitive, whitespace-stripped).
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Affected products
jahlives · openssl_encryptRelated CVEs — jahlives openssl_encrypt
In the same product, most dangerous first.
CVE-2026-74899CRITICALopenssl_encrypt before 1.4.0 Sandbox Escape via Type HierarchyEPSS 0.8%CVE-2026-74878CRITICALopenssl_encrypt before 1.4.0 TOTP Rate Limiter BypassEPSS 0.7%CVE-2026-81690HIGHverify-usb before 1.4.9 Symlink Directory Traversal Code ExecutionEPSS 0.7%CVE-2026-74886CRITICALopenssl_encrypt before 1.4.0 Plugin Import Guard BypassEPSS 0.7%CVE-2026-74895CRITICALopenssl_encrypt before 1.4.0 Plugin Sandbox Bypass via Process IsolationEPSS 0.7%CVE-2026-74872CRITICALopenssl_encrypt before 1.4.0 Arbitrary Code Execution via WhirlpoolEPSS 0.7%