Which versions of openssl_encrypt are affected by EUVD-2026-60108?

The openssl_encrypt Python library (versions before 1.4.0) contains a critical cryptographic vulnerability that weakens encryption key security, increasing risk of data compromise for any application…. A patch is available.

How to fix or mitigate EUVD-2026-60108?

Within 24 hours, conduct an immediate inventory of all applications and systems using openssl_encrypt library and identify current versions in production. Within 7 days, upgrade all instances to version 1.4.0 or later in a test environment, validate functionality, and begin staged deployment to production systems. Within 30 days, complete full production deployment of version 1.4.0 across all systems, perform mandatory key rotation for all data encrypted with vulnerable versions to eliminate weak keys from the environment, and document remediation completion.

openssl_encrypt EUVD-2026-60108

Q: What is the CVSS score of EUVD-2026-60108?

EUVD-2026-60108 has a CVSS 4.0 base score of 9.3 (Critical). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

| CVE-2026-74889 CRITICAL

Inadequate Encryption Strength (CWE-326)

2026-08-17 VulnCheck

GHSA-fxcp-mjj5-v58w

Information Disclosure Openssl Encrypt Jahlives

9.3

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

9.3 CRITICAL

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

5.9 MEDIUM

Deterministic key derivation weakens confidentiality against multi-target attacks (C:H), but requires collected ciphertexts and cryptanalysis (AC:H); no direct integrity or availability impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Aug 17, 2026 - 13:08 vuln.today

Patch available

Aug 17, 2026 - 12:01 EUVD

CVE Published

Aug 17, 2026 - 11:04 cve.org

CRITICAL 9.3

DescriptionCVE.org

openssl_encrypt versions before 1.4.0 use HKDF with no salt and static info parameter in key normalization functions, reducing entropy extraction and determinism. Attackers can exploit predictable key derivation with identical inputs to weaken cryptographic security against multi-target attacks.

AnalysisAI

Weak cryptographic key derivation in the openssl_encrypt Python library (all versions before 1.4.0) stems from its key-normalization routines invoking HKDF with no salt and a static info parameter, making derived keys deterministic for identical inputs. This reduces effective entropy and weakens resistance to multi-target (batch) attacks, letting an adversary who collects ciphertexts or derived-key material amortize cryptanalytic effort across many victims. No public exploit identified at time of analysis; the flaw was reported by VulnCheck and a vendor patch is available in 1.4.0.

Technical ContextAI

openssl_encrypt is a Python encryption utility/library (PyPI project 'jahlives:openssl_encrypt') that wraps symmetric encryption workflows. HKDF (HMAC-based Key Derivation Function, RFC 5869) is designed as extract-then-expand: the extract step is meant to be seeded with a random, per-operation salt to bind derived keys to unique contexts, and the info parameter provides domain separation. By calling HKDF with an empty/absent salt and a fixed static info string, the library collapses these protections so that the same input key material always maps to the same output key. This is the classic CWE-326 (Inadequate Encryption Strength) failure mode - the primitive is sound but is configured to remove randomization, undermining the entropy-extraction guarantees HKDF normally provides.

RemediationAI

Upgrade to openssl_encrypt 1.4.0 or later, which is the vendor-released patched version fixing the HKDF key-derivation weakness; consult the GitHub Security Advisory GHSA-j9mh-57cc-665x (https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-j9mh-57cc-665x) and the VulnCheck advisory for confirmation. Because the defect is in how keys are derived, patching alone does not retroactively secure data already encrypted with weak keys - plan to re-encrypt or rotate any keys/ciphertexts produced by versions before 1.4.0, accepting the operational cost of a re-encryption pass. If an immediate upgrade is not possible, a compensating control is to supply your own randomly generated per-operation salt to HKDF (rather than relying on the library's default empty salt) and unique info values where the API permits, and to avoid reusing identical input key material across targets; the trade-off is that this requires code changes at every call site and careful key-management discipline.