Is CVE-2026-81715 exploited in the wild?

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

How severe is CVE-2026-81715?

Medium severity, with a CVSS score of 4, published 27 August 2026.

Which products and versions are affected?

Jahlives Openssl Encrypt <=1.4.8; openssl-encrypt (PyPI) ECOSYSTEM:introduced=0,fixed=1.4.9.

Is there a fix for CVE-2026-81715?

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

It is attacked with local access.

Am I affected by CVE-2026-81715?

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-81715: openssl-encrypt credential exposure in debug output

Q: Is there a fix for CVE-2026-81715?

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.

Q: How is CVE-2026-81715 attacked?

It is attacked with local access.

Q: Am I affected by CVE-2026-81715?

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-81715 · Severity: medium · CVSS 4 · Published 2026-08-27

openssl-encrypt is a Python library that manages cryptographic keys via a keyserver. When run with debug logging enabled, the library fails to redact authentication tokens, causing them to be written in plaintext to logs and terminal history. An attacker with access to logs, terminal history, or error output could capture these credentials and authenticate to the keyserver.

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

Quick answers

Is CVE-2026-81715 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-81715 being exploited in the wild.
How severe is CVE-2026-81715?: Medium severity, with a CVSS score of 4, published 27 August 2026.
Which products and versions are affected?: Jahlives Openssl Encrypt <=1.4.8; openssl-encrypt (PyPI) ECOSYSTEM:introduced=0,fixed=1.4.9.
Is there a fix for CVE-2026-81715?: 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-81715 attacked?: It is attacked with local access.
Am I affected by CVE-2026-81715?: 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 information disclosure (CWE-532) caused by insufficient sanitization of debug output. The `sanitize_argv_for_debug` function fails to redact the keyserver bearer token passed as a positional argument to the `keyserver set-token` command. As a result, when the application runs with the `--debug` flag, the token is printed in cleartext to stderr even without `--unsafe-show-secrets` being specified. This persists credentials in shell history and log files. The vulnerability affects versions <= 1.4.8 and was fixed in version 1.4.9 by routing the positional token through the debug_secret redaction mechanism.

Affected products

jahlives openssl-encrypt <=1.4.8

Identifiers

CVE-2026-81715
PYSEC-2026-3964

Timeline

2026-08-12: disclosed
2026-08-27: patched: Version 1.4.9 released with fix

References

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