Is CVE-2026-81704 exploited in the wild?

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

How severe is CVE-2026-81704?

High severity, with a CVSS score of 7.5, published 27 August 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2026-81704?

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

It is attacked over the network.

Am I affected by CVE-2026-81704?

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-81704: openssl_encrypt weak key derivation in D-Bus EncryptFile handler

CVE-2026-81704 · Severity: high · CVSS 7.5 · Published 2026-08-27

openssl_encrypt is a Python library for encrypting files. The D-Bus service component used to encrypt files via system or session bus was deriving encryption keys using only SHA-256 hashing without proper stretching, rather than the documented Argon2id algorithm. This makes encrypted files vulnerable to offline password guessing attacks that are millions of times faster than intended, potentially exposing encrypted data if an attacker obtains the files.

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

Quick answers

Is CVE-2026-81704 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-81704 being exploited in the wild.
How severe is CVE-2026-81704?: High severity, with a CVSS score of 7.5, published 27 August 2026.
Which products and versions are affected?: Jahlives Openssl Encrypt before 1.4.9; openssl-encrypt (PyPI) ECOSYSTEM:introduced=0,fixed=1.4.9.
Is there a fix for CVE-2026-81704?: 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-81704 attacked?: It is attacked over the network.
Am I affected by CVE-2026-81704?: 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 a weak key derivation failure (CWE-916) in the D-Bus CryptoService.EncryptFile handler. The handler constructed a hash configuration dictionary with incorrect key names that the key-derivation core does not recognize, causing the core to skip KDF application entirely and fall back to a single unstretched SHA-256 hash of the password and salt. This results in offline password guessing being approximately 10^6–10^7 times faster than intended (roughly 10^10 SHA-256 operations per second on commodity GPUs versus 10^3 per second against Argon2id with 64 MiB memory cost). The vulnerability affects only files encrypted via the D-Bus service; CLI and GUI encryption paths are unaffected. Version 1.4.9 fixes the issue by moving key derivation configuration to a dedicated module that correctly constructs the config structure and enforces Argon2id by default, rejecting encryption requests that do not meet minimum work-factor requirements. Affected versions are 1.4.8 and earlier; the D-Bus service was removed entirely in the 1.5.x line.

Affected products

jahlives openssl_encrypt before 1.4.9

Identifiers

CVE-2026-81704
PYSEC-2026-3963

Timeline

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

References

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