Vulnerability Description
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 Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Jahlives | Openssl Encrypt | < 1.4.9 |
Related Weaknesses (CWE)
References
- https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-xg52-638v-jVendor Advisory
- https://www.vulncheck.com/advisories/openssl-encrypt-before-1.4.9-plugin-signingThird Party Advisory
FAQ
What is CVE-2026-81714?
CVE-2026-81714 is a vulnerability with a CVSS score of 7.0 (HIGH). 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 (forg...
How severe is CVE-2026-81714?
CVE-2026-81714 has been rated HIGH with a CVSS base score of 7.0/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-81714?
Check the references section above for vendor advisories and patch information. Affected products include: Jahlives Openssl Encrypt.