CVE-2026-74888

openssl_encrypt before 1.4.0 Non-Standard PBKDF2 Key Derivation

Published Aug 17, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
openssl_encrypt versions before 1.4.0 use a non-standard PBKDF2 key derivation construction with iterations=1 per call in an outer loop, creating a KDF whose security properties have not been formally analyzed. Attackers can exploit this weakened key derivation to more efficiently crack passwords protecting legacy encrypted files compared to standard PBKDF2 implementations.

Analysis

AI-generated

Technical impact

The vulnerability arises from a non‑standard PBKDF2 key derivation in the openssl_encrypt library versions before 1.4.0. It employs iterations=1 per call within an outer loop, resulting in a KDF with unverified security properties. Attackers can thus reduce the effort required to crack passwords protecting legacy encrypted files compared to standard PBKDF2 implementations. This weakness directly lowers the cost of offline brute‑force attacks.

Affected Systems

Affected systems include the jahlives open-source project openssl_encrypt. Any deployments using this library with a version older than 1.4.0 are vulnerable. No specific distribution packages are listed, so the impact extends to any build that incorporates the legacy code. Users must verify their installed version and update accordingly.

Risk and Exploitability

The CVSS score of 8.7 indicates a high severity issue. The EPSS score is not available, and it is not currently listed in the KEV catalog. The likely attack vector is offline password cracking against encrypted files that use the legacy key derivation. Because the weakness only applies when the same key is derived repeatedly, an attacker who obtains an encrypted file can perform a targeted brute‑force attack with significantly reduced effort. Prompt patching mitigates the risk entirely.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the openssl_encrypt library to version 1.4.0 or later, which uses a standard PBKDF2 implementation.
  • Re‑encrypt existing data with a more secure key derivation, if possible.
  • Employ stronger passwords and, where supported, increase PBKDF2 iteration counts in any custom applications.

Generated by OpenCVE AI on August 17, 2026 at 12:55 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:*:*:*
Type Values Removed Values Added
CPEs cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:python:*:*
Type Values Removed Values Added
First Time appeared Jahlives
Jahlives openssl Encrypt
Vendors & Products Jahlives
Jahlives openssl Encrypt
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description openssl_encrypt versions before 1.4.0 use a non-standard PBKDF2 key derivation construction with iterations=1 per call in an outer loop, creating a KDF whose security properties have not been formally analyzed. Attackers can exploit this weakened key derivation to more efficiently crack passwords protecting legacy encrypted files compared to standard PBKDF2 implementations.
Title openssl_encrypt before 1.4.0 Non-Standard PBKDF2 Key Derivation
Weaknesses CWE-327
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-327

    Use of a Broken or Risky Cryptographic Algorithm

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 1, 2026, 3:20 PM
Reserved
Aug 17, 2026, 10:42 AM
Status
Analyzed
Published
Aug 17, 2026, 11:16 AM
Modified
Sep 1, 2026, 3:26 PM