Is CVE-2026-81686 exploited in the wild?

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

How severe is CVE-2026-81686?

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

Which products and versions are affected?

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

Is there a fix for CVE-2026-81686?

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

It is attacked with local access, in a software library.

Am I affected by CVE-2026-81686?

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-81686: openssl_encrypt D-Bus Properties.Set authorization bypass

CVE-2026-81686 · Severity: medium · CVSS 6.2 · Published 2026-08-27

openssl_encrypt is a cryptography service library that includes an optional D-Bus daemon for managing encryption operations. A local attacker can bypass authorization checks on the D-Bus service and modify critical configuration parameters without permission, causing the service to reject all encryption requests or become unstable. This results in a persistent denial of service affecting any applications relying on the crypto service.

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

Quick answers

Is CVE-2026-81686 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-81686 being exploited in the wild.
How severe is CVE-2026-81686?: Medium severity, with a CVSS score of 6.2, published 27 August 2026.
Which products and versions are affected?: Jahlives Openssl Encrypt 1.4.x before 1.4.9; openssl-encrypt (PyPI) ECOSYSTEM:introduced=0,fixed=1.4.9.
Is there a fix for CVE-2026-81686?: 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-81686 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-81686?: 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 D-Bus Properties.Set method in openssl_encrypt 1.4.x lacks both polkit authorization checks (CWE-862) and input validation (CWE-20). An unauthenticated local user on the system bus can invoke Set to modify MaxConcurrentOperations (setting it to 0, negative values, or excessive values) or unbounded DefaultTimeout parameters. Setting MaxConcurrentOperations to 0 or negative values causes the concurrency gate to permanently refuse all operations; setting it to very large values removes rate limiting. The vulnerability affects only the 1.4.x line; the D-Bus service was removed in 1.5.x. The fix in version 1.4.9 adds polkit authorization under the dedicated ch.rmrf.openssl_encrypt.configure action and validates parameters against safe bounds, rejecting invalid values.

Affected products

jahlives openssl_encrypt 1.4.x before 1.4.9

Identifiers

CVE-2026-81686
PYSEC-2026-3794

Timeline

2026-08-27: disclosed
2026-08-12: 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.