/

CVE-2026-81718

Severity:

HIGH RISK

(7.5)

Weak KDF Parameters (CWE-326) in openssl_encrypt Files

CVE-2026-81718

Deferred

Vulnerability type

Category:

Insufficient Cryptographic Work Factor

CWE:

CWE-326

Impact:

Offline Password Cracking and Potential Private Key Disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

openssl_encrypt versions before 1.4.9 use relatively low PBKDF2-HMAC-SHA256 iteration counts when protecting post-quantum cryptography keyfile private keys and verifying dual-encryption file passwords. If an attacker obtains keyfiles or encrypted files, they may perform offline password guessing accelerated by GPUs or ASICs.

Affected context

The vulnerability occurs in deployments that use openssl_encrypt to protect PQC keyfile private keys or perform dual-encryption file-password verification. Risk increases when encrypted files or keyfiles are exposed and the associated passwords are weak, reused, predictable, or otherwise susceptible to guessing.

Exploit preconditions

  • Attack surface: Offline access to encrypted keyfiles or encrypted data
  • Required access: Ability to obtain the protected file or keyfile; direct service access is generally not required
  • Trigger point: Password-guessing attempts against the PBKDF2-derived protection or verification value
  • Why exploitation is possible: The configured PBKDF2 iteration counts provide a limited computational cost, allowing many guesses to be tested with specialized hardware

Why this happens

The underlying issue is an insufficient cryptographic work factor in password-based key derivation. PBKDF2-HMAC-SHA256 is used with iteration counts that may be too low for current GPU- and ASIC-assisted offline attacks, particularly when attackers can test guesses without interacting with the application.

This maps to CWE-326: Inadequate Encryption Strength, because the effective protection is weakened by parameters that do not impose sufficient computational cost on password guesses.

Potential impact

  • Attackers may recover weak or reused wrapping passwords through offline guessing
  • Private keys stored in protected keyfiles could be exposed
  • Encrypted files may be decrypted if the corresponding password is recovered
  • Compromised keys could enable impersonation, unauthorized decryption, or access to protected systems
  • Organizations may face broader compromise when passwords or keys are reused across environments

General mitigation guidance

Mitigation typically focuses on increasing the cost of password-based key derivation and reducing reliance on guessable secrets.

Common defensive patterns include:

  • Use password-based key derivation parameters with a work factor appropriate for current hardware and threat models
  • Prefer memory-hard password derivation where the surrounding format and interoperability requirements support it
  • Require long, unique, high-entropy passwords or passphrases for keyfile and file protection
  • Use authenticated encryption and well-defined, versioned encryption formats
  • Limit password reuse and protect derived keys and private keys with appropriate access controls
  • Apply least privilege to processes that read keyfiles and encrypted data
  • Consider hardware-backed key protection where suitable for the deployment

How teams detect issues like this

Organizations can identify this class of issue through:

  • Static analysis and configuration checks for low PBKDF2 iteration counts or weak password-derived key settings
  • Code review of key derivation, encryption-format, and password-verification implementations
  • Inventory checks that identify legacy encrypted files or keyfiles using weak derivation parameters
  • Policy enforcement requiring approved KDF algorithms, minimum work factors, unique salts, and authenticated encryption
  • Testing that measures password-guessing cost using representative hardware, including accelerated platforms
  • Automated security review tools that flag inadequate cryptographic parameters and password-based encryption patterns

Sources

SourceLink
github.comgithub.com/jahlives/openssl_encrypt/security/advisories/GHSA-fmjx-p826-6fvr
vulncheck.comvulncheck.com/advisories/openssl-encrypt-before-1.4.9-weak-cryptographic-parameters

Frequently asked

questions

Usually, exploitation is offline rather than directly remote. An attacker must first obtain an encrypted file or keyfile and then perform password guessing without repeatedly contacting the protected service.

The key prerequisite is access to the encrypted artifact. Additional access may be required to obtain related metadata or to use any recovered password or private key.

Use a modern, adequately tuned password-based key derivation design with a sufficiently high computational or memory cost, combined with strong unique passwords and authenticated encryption.

Establish cryptographic parameter policies, review encryption code centrally, test resistance to offline guessing, avoid password reuse, and periodically reassess work factors as hardware capabilities improve.

Find out what's already
exploitable in your codebase.