How severe is CVE-2026-81715?

CVE-2026-81715 has a CVSS 3.x base score of 3.3, rated low severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2026-81715 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (9th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-81715?

CVE-2026-81715 affects Jahlives Openssl Encrypt. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-81715?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-81715 published?

CVE-2026-81715 was published on 2026-08-27 and last updated on 2026-09-03.

CVE-2026-81715

CVE-2026-81715 is a low-severity vulnerability in Jahlives Openssl Encrypt with a CVSS 3.x base score of 3.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-532.

Key facts

Severity: Low (CVSS 3.x base score 3.3)
CVSS v4: 8.7
EPSS exploit prediction: 0% (9th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-532
Affected product: Jahlives Openssl Encrypt
Published: 2026-08-27
Last modified: 2026-09-03

Description

openssl_encrypt (pip package openssl-encrypt) versions <= 1.4.8 do not redact the keyserver bearer token passed as the positional argument to 'keyserver set-token' in the --debug argv dump, because sanitize_argv_for_debug fails to sanitize it. As a result the token is printed in cleartext to stderr under --debug (even without --unsafe-show-secrets), persisting the credential in logs and terminal history. Fixed in 1.4.9.

Frequently asked questions

What is CVE-2026-81715?: openssl_encrypt (pip package openssl-encrypt) versions <= 1.4.8 do not redact the keyserver bearer token passed as the positional argument to 'keyserver set-token' in the --debug argv dump, because sanitize_argv_for_debug fails to sanitize it. As a result the token is printed in cleartext to stderr under --debug (even without --unsafe-show-secrets), persisting the credential in logs and terminal history. Fixed in 1.4.9.
How severe is CVE-2026-81715?: CVE-2026-81715 has a CVSS 3.x base score of 3.3, rated low severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2026-81715 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (9th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-81715?: CVE-2026-81715 affects Jahlives Openssl Encrypt. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-81715?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-81715 published?: CVE-2026-81715 was published on 2026-08-27 and last updated on 2026-09-03.

References

Affected products (1)

cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:python:*:*

More vulnerabilities in Jahlives Openssl Encrypt

CVE-2026-81702 — Critical (CVSS 9.8): openssl_encrypt before 1.4.9 fails to re-derive and validate fingerprints when loading identities from identity.json,…
CVE-2026-81701 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.9 use a denylist to identify trusted built-in plugins, allowing unsigned plugins in…
CVE-2026-81700 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.9 contain a signature verification vulnerability in gpg_runner.verify_detached that…
CVE-2026-74901 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.0 contain an authentication bypass vulnerability in pqc.py where AES-GCM decryption…
CVE-2026-74900 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.0 contain a critical vulnerability in pqc.py where KEM decapsulation failures…
CVE-2026-74899 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.0 contain a sandbox escape vulnerability in IsolatedPluginExecutor that exposes…

All CVEs affecting Jahlives Openssl Encrypt →

Other CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities

CVE-2022-36407 — Critical (CVSS 9.9): Insertion of Sensitive Information into Log File vulnerability in Hitachi Virtual Storage Platform, Hitachi Virtual…
CVE-2023-40029 — Critical (CVSS 9.9): Argo CD is a declarative continuous deployment for Kubernetes. Argo CD Cluster secrets might be managed declaratively…
CVE-2021-32724 — Critical (CVSS 9.9): check-spelling is a github action which provides CI spell checking. In affected versions and for a repository with the…
CVE-2026-49200 — Critical (CVSS 9.8): The acer_cgi.log file in the device firmware is accessible without authentication via the web interface. This file…
CVE-2026-22778 — Critical (CVSS 9.8): vLLM is an inference and serving engine for large language models (LLMs). From 0.8.3 to before 0.14.1, when an invalid…
CVE-2025-11008 — Critical (CVSS 9.8): The CE21 Suite plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and…

Browse all CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities →