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).

CVE-2026-81714 affects openssl-encrypt (pip package) versions <= 1.4.8, which use suffix-tolerant fingerprint matching in the enroll_trust_key function when binding a plugin-signing trust anchor. An attacker can exploit this by crafting a GPG key with a short (~32-bit) key ID that collides with a legitimate key. If an operator confirms this short key ID, the attacker's key is enrolled as a trusted anchor. Under the ENFORCE signature policy, this trusted anchor can then vouch for malicious plugins, enabling supply chain-style attacks via unsigned or attacker-signed plugins. Version 1.4.9 addresses the vulnerability by requiring an exact match against the full primary-key fingerprint (case-insensitive, whitespace-stripped). Operators using openssl-encrypt should upgrade to version 1.4.9 immediately.