PT-2026-85197

openssl encrypt before 1.4.9 executes untrusted third-party plugins with insufficient controls: the plugin signature policy defaulted to WARN, so an unsigned/unverifiable non-built-in plugin was compiled and executed in the host process at import time, before the runtime sandbox is installed. The...

PT-2026-85195

openssl encrypt pip: openssl-encrypt versions before 1.4.9 contain a path traversal flaw in PluginSandbox. is safe path, which authorized file access using a bare string-prefix match. A sandboxed plugin without the READ FILES permission could read or write another plugin's directory that merely...

PT-2026-82614

Name of the Vulnerable Software and Affected Versions openssl encrypt versions prior to 1.4.9 Description Insufficient controls during the execution of untrusted third-party plugins allow for arbitrary code execution with the privileges of the user running the software. This occurs because the...

PT-2026-82595

Name of the Vulnerable Software and Affected Versions openssl-encrypt versions prior to 1.4.9 Description The software fails to sanitize filenames read from untrusted drive data located outside the AES-GCM authenticated manifest before displaying them in the output of the verify-usb command. An...

PT-2026-82610

Name of the Vulnerable Software and Affected Versions openssl-encrypt versions prior to 1.4.9 Description The sanitize argv for debug function fails to sanitize the keyserver bearer token when passed as a positional argument to the 'keyserver set-token' command. Consequently, when the --debug fla...

PT-2026-82593

Name of the Vulnerable Software and Affected Versions openssl encrypt versions prior to 1.4.9 Description The software fails to validate the 36-bit STREAMINFO total samples field of FLAC files before using it to size a memory allocation within the np.random.randintsize=total samples, channels...

PT-2026-85191

openssl-encrypt pip package before 1.4.9 contains a symlink-following flaw in its verify-usb v2 added-file allowlist scan. The scan enumerated the drive with rglob, which in CPython does not descend into symlinked directories and treats the symlink as an ordinary directory, while O NOFOLLOW on th...

PT-2026-82599

Name of the Vulnerable Software and Affected Versions openssl encrypt versions prior to 1.4.9 Description A shell injection issue exists in the info command's reconstructed CLI block. The system interpolates untrusted metadata fields without proper quoting, allowing attackers to craft metadata...

PT-2026-82608

Name of the Vulnerable Software and Affected Versions openssl encrypt versions prior to 1.4.9 Description The software fails to sanitize the email field of imported identity documents. This allows attackers to inject ANSI escape sequences—special codes used to control terminal formatting—to forge...

PT-2026-82598

Name of the Vulnerable Software and Affected Versions openssl-encrypt versions prior to 1.4.9 Description A configuration file resolution flaw exists in crypt settings.py where the CONFIG FILE variable is reassigned to a relative path. This causes the legacy Tk GUI's SettingsTab to read and write...

PT-2026-82582

openssl encrypt pip package openssl-encrypt versions = 1.4.8 advertise a portable USB workspace as an 'Encrypted USB Workspace' with AES-256-GCM encryption and write a marker declaring the workspace encrypted, but the workspace directory is actually stored in cleartext and the derived encryption...

PT-2026-82581

Name of the Vulnerable Software and Affected Versions openssl encrypt versions prior to 1.4.9 Description Failure to authenticate the presence of recovery slots in envelope-format encrypted files allows attackers to remove these slots without re-encrypting the payload. By modifying the file heade...

PT-2026-82583

Name of the Vulnerable Software and Affected Versions openssl encrypt versions prior to 1.4.9 Description The desktop GUI writes decrypted plaintext using world-readable default permissions. This allows unprivileged local users on multi-user systems to read the decrypted output files...

PT-2026-82597

openssl encrypt versions before 1.4.9 fail to sanitize terminal control characters in file metadata printed by the info command. Attackers can craft malicious files containing escape sequences to repaint terminal output and forge verification information displayed to users...

PT-2026-82589

openssl encrypt versions before 1.4.9 store an unkeyed SHA-256 hash of the plaintext in the cleartext file header metadata. Attackers can read this hash without the password to confirm guessed plaintexts offline or fingerprint identical plaintexts across separately-encrypted files...

PT-2026-82605

Name of the Vulnerable Software and Affected Versions openssl encrypt versions prior to 1.4.9 Description The D-Bus CryptoService.EncryptFile handler uses unstretched SHA-256 instead of Argon2id for key derivation. This allows attackers to perform offline password guessing against encrypted files...

PT-2026-82607

Name of the Vulnerable Software and Affected Versions openssl encrypt versions prior to 1.4.9 Description The software fails to prevent namespace collisions between own identities and contacts within the IdentityStore. This allows attackers to create shadowed contact entries that remain invisible...

Lemur: Server-Side Request Forgery via the ACME client following server-controlled URLs

SummaryThe ACME client used to issue certificates from Let's Encrypt / Google Public CA / private ACME CAs connects to an acmeurl, then issues requests to URLs that the ACME server returns in its directory/order/authorization/finalize responses - this is the classic ACME-client SSRF RFC 8555...

PT-2026-79975

Cleartext storage in PostgreSQL pgcrypto disabled ciphers allows a user to recover cleartext, via direct observation of the faulty ciphertext. The OpenSSL version and OpenSSL configuration determine the disabled ciphers. If the application accepts encrypted data as input, decryption will succeed...

Lemur: Server-Side Request Forgery via the ACME client following server-controlled URLs

Summary The ACME client used to issue certificates from Let's Encrypt / Google Public CA / private ACME CAs connects to an acmeurl, then issues requests to URLs that the ACME server returns in its directory/order/authorization/finalize responses - this is the classic ACME-client SSRF RFC 8555...