CVE-2026-81714

High

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

SeverityHigh

CVSS7.0

Exploit probability—

ProductJahlives Openssl Encrypt

PublishedAug 27, 2026

First seenAug 27, 2026

Weakness typeCWE-347CWE-347

How to fix

Update

jahlives openssl_encrypt1.4.9 or later
openssl-encrypt1.4.9 or later

Vendor advisories

github.com/jahlives/openssl_encrypt/security/advisories/GHSA-xg52-638v-jc5m

Affected products

Product	Affected versions	Fixed in
jahlives openssl_encrypt	v < 1.4.9	1.4.9
openssl-encryptPyPI	v < 1.4.9	1.4.9

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.