Is CVE-2026-81694 exploited in the wild?

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

How severe is CVE-2026-81694?

Medium severity, with a CVSS score of 4, 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-81694?

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-81694 attacked?

It is attacked with local access.

Am I affected by CVE-2026-81694?

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-81694: openssl-encrypt output injection via unsanitized filenames

CVE-2026-81694 · Severity: medium · CVSS 4 · Published 2026-08-27

openssl-encrypt is a Python package that encrypts and verifies USB drive contents using AES-GCM. The verify-usb command can be deceived by an attacker who crafts malicious filenames on the USB drive; these filenames contain terminal control codes that overlay a fake "PASSED" message on the output, masking the actual detection of drive tampering. This allows attackers to hide evidence of data compromise from security checks.

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

Quick answers

Is CVE-2026-81694 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-81694 being exploited in the wild.
How severe is CVE-2026-81694?: Medium severity, with a CVSS score of 4, 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-81694?: 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-81694 attacked?: It is attacked with local access.
Am I affected by CVE-2026-81694?: 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 output injection flaw (CWE-117) in the verify-usb command. The root cause is the failure to sanitize filenames read from untrusted drive data before printing them in verification reports. An attacker can embed ANSI escape sequences (cursor-movement and erase-line control bytes) into filenames on the drive; when printed unsanitized to the terminal, these sequences repaint the output to display a forged PASSED verdict, overwriting the actual FAILED status. No authentication is required—the attacker only needs to modify files on the target USB drive. The fix, released in version 1.4.9, routes all drive-derived filenames through the sanitize_for_display() function before output.

Affected products

openssl-encrypt openssl-encrypt <=1.4.8

Identifiers

CVE-2026-81694
PYSEC-2026-3960

Timeline

2026-08-12: disclosed: GitHub Security Advisory GHSA-c793-rj9w-r3wg published
2026-08-27: advisory: CVE-2026-81694 published on NVD
2026-08-27: patched: Fix released in version 1.4.9

References

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