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).
References
| Link | Resource |
|---|---|
| https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-xg52-638v-jc5m | Vendor Advisory |
| https://www.vulncheck.com/advisories/openssl-encrypt-before-1.4.9-plugin-signing-trust-anchor-enrollment-bypass | Third Party Advisory |
Configurations
History
No history.
Information
Published : 2026-08-27 17:21
Updated : 2026-09-02 13:09
NVD link : CVE-2026-81714
Mitre link : CVE-2026-81714
CVE.ORG link : CVE-2026-81714
JSON object : View
Products Affected
jahlives
- openssl_encrypt
CWE
CWE-347
Improper Verification of Cryptographic Signature
