Is CVE-2026-81714 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-81714 being exploited in the wild.

How severe is CVE-2026-81714?

High severity, with a CVSS score of 7, published 27 August 2026.

Which products and versions are affected?

openssl-encrypt (PyPI) ECOSYSTEM:introduced=0,fixed=1.4.9.

Is there a fix for CVE-2026-81714?

Yes. openssl-encrypt (PyPI): upgrade to 1.4.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-81714 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-81714?

Check whether you run Jahlives Openssl Encrypt or openssl-encrypt (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-81714: openssl-encrypt cryptographic signature verification bypass

CVE-2026-81714 · Severity: high · CVSS 7 · Published 2026-08-27

openssl-encrypt is a Python library for plugin signing and trust-anchor management. Versions 1.4.8 and earlier accept partial GPG key fingerprints during trust enrollment, allowing an attacker to forge a short (32-bit) key ID that collides with a legitimate key. Once enrolled, the attacker's key can sign malicious plugins that are trusted by the system, leading to arbitrary code execution through the ENFORCE signature policy.

Technologies: Jahlives Openssl Encrypt, openssl-encrypt (PyPI). Vendors: Jahlives, PyPI.

Quick answers

Is CVE-2026-81714 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-81714 being exploited in the wild.
How severe is CVE-2026-81714?: High severity, with a CVSS score of 7, published 27 August 2026.
Which products and versions are affected?: openssl-encrypt (PyPI) ECOSYSTEM:introduced=0,fixed=1.4.9.
Is there a fix for CVE-2026-81714?: Yes. openssl-encrypt (PyPI): upgrade to 1.4.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-81714 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-81714?: Check whether you run Jahlives Openssl Encrypt or openssl-encrypt (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

openssl-encrypt (PyPI): upgrade to 1.4.9 or later
```
pip install "openssl-encrypt>=1.4.9"
```

Technical details

The vulnerability is an improper cryptographic signature verification flaw (CWE-347) in the enroll_trust_key function. It uses suffix-tolerant fingerprint matching instead of requiring exact full-fingerprint validation, allowing an operator to confirm only a short, forgeable GPG key ID. An attacker can generate a colliding key with the same short ID, enroll it as a trusted anchor, and use it to sign malicious plugins that pass validation under the ENFORCE policy. The attack requires operator interaction to confirm the fingerprint but exploits the partial-match acceptance to bypass key verification. Version 1.4.9 fixes this by enforcing exact full primary-key fingerprint matches (case-insensitive, whitespace-stripped) and rejecting partial confirmations.

Affected products

openssl-encrypt openssl-encrypt 0 to 1.4.8

Identifiers

CVE-2026-81714
PYSEC-2026-3799

Timeline

2026-08-27: disclosed
2026-08-12: patched: Version 1.4.9 released with fix

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.