CVE-2026-81694

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

Published Aug 27, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
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().

Analysis

AI-generated

Technical impact

An attacker can exploit the openssl-encrypt package by placing filenames containing terminal control sequences on an untrusted USB drive. When the verify-usb command outputs the list of files, those control characters are interpreted by the terminal, repainting the screen with a forged PASSED verdict. This deceives the user into believing the device has passed verification while in fact tampering has been detected.

Affected Systems

The vulnerability affects the Jahlives openssl-encrypt Python package, versions 1.4.8 and older. Any environment that installs this package from PyPI and uses the verify-usb command to validate USB devices is potentially impacted.

Risk and Exploitability

The CVSS score of 9.3 classifies this flaw as critical. Because the vulnerability is only exercised when the verify-usb command is run, the likely attack vector is a compromised USB drive that a user attaches to an affected system. The EPSS score is not available, and the flaw is not listed in the CISA KEV catalog, indicating no publicly known exploits. The exploit provides no direct code execution; instead, it manipulates terminal output to mask tampering, potentially enabling a misled user to accept compromised devices.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the openssl-encrypt Python package to version 1.4.9 or later, which sanitizes filenames before display.
  • Restrict or remove the verify-usb command from systems that do not require it, preventing accidental misuse.
  • Audit USB device filenames and ensure no untrusted devices are connected to production environments.

Generated by OpenCVE AI on August 27, 2026 at 18:00 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Title verify-usb before 1.4.9 Output Injection via Unsanitized Filenames openssl-encrypt before 1.4.9 Output Injection via Unsanitized Filenames in verify-usb Command
Type Values Removed Values Added
CPEs cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:*:*:*
Type Values Removed Values Added
CPEs cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:python:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Jahlives
Jahlives openssl Encrypt
Vendors & Products Jahlives
Jahlives openssl Encrypt
Type Values Removed Values Added
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().
Title verify-usb before 1.4.9 Output Injection via Unsanitized Filenames
Weaknesses CWE-117
References
Metrics cvssV3_1

{'score': 3.3, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N'}

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-117

    Improper Output Neutralization for Logs

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 29, 2026, 9:16 PM
Reserved
Aug 27, 2026, 11:12 AM
Status
Analyzed
Published
Aug 27, 2026, 5:20 PM
Modified
Sep 3, 2026, 3:08 PM