CVE-2026-81694 openssl-encrypt before 1.4.9 Output Injection via Unsanitized Filenames in verify-usb Command

Critical 9.3 Published Updated

Attackers can forge verification results by injecting terminal control characters into filenames, masking tampering in USB drives.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-81694?

CVE-2026-81694 is a critical vulnerability in Jahlives Openssl Encrypt, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

openssl-encrypt (pip package, versions <= 1.4.8) fails to sanitize filenames read from untrusted drive data (outside the AES-GCM authenticated manifest) before printing them in the verify-usb command's output. An attacker can plant filenames containing terminal cursor-movement and erase-line control bytes that repaint a forged PASSED verdict on screen, masking actual tamper detection. Fixed in 1.4.9 by routing drive-derived names through sanitize_for_display().

Weakness: CWE-117

Which versions are affected by CVE-2026-81694?

1 open source package ship an affected version, including openssl-encrypt. It affects 1 product.

PackageAffectedFixed in
openssl-encrypt PyPIAll versions1.4.9

Products include Jahlives Openssl Encrypt.

How do I fix CVE-2026-81694?

Upgrade openssl-encrypt to 1.4.9 or later.

Is CVE-2026-81694 being exploited?

There is no known exploitation of CVE-2026-81694 in the wild and no public exploit code.

All Jahlives Openssl Encrypt vulnerabilities

Sources

Also known as GHSA-9grr-c5h5-3w4h, GHSA-c793-rj9w-r3wg, PYSEC-2026-3960.

Is CVE-2026-81694 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free