High · CVSS 8.7CVE-2026-81718

openssl_encrypt before 1.4.9 Weak Cryptographic ParametersCVE-2026-81718

Answer in brief

CVE-2026-81718 records a High severity (CVSS 8.7) vulnerability in openssl_encrypt before 1.4.9 Weak Cryptographic Parameters. The current sources do not mark it as known exploited. The current feed maps jahlives/openssl_encrypt (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 27, 2026Updated Oct 1, 2026Source checked Oct 11, 2026First seen by HOL Aug 27, 2026Material review Oct 1, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.7
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 8.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps jahlives/openssl_encrypt (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
jahlives/openssl_encryptgeneric	>=0 <1.4.9	1.4.9

Recommended response

Check inventory. Check lockfiles and deployed manifests for jahlives/openssl_encrypt.
Review the reported fix. Update jahlives/openssl_encrypt to 1.4.9 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 1, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 27, 2026

Sources and claim methodology

Upstream source description

openssl_encrypt versions before 1.4.9 use under-parameterized PBKDF2-HMAC-SHA256 with only 100,000 iterations to protect PQC keyfile private keys and 10,000 iterations for dual-encryption file-password verification. Attackers who obtain keyfiles or encrypted files can brute-force wrapping passwords offline using GPU or ASIC acceleration.

Quoted source text, attributed separately from HOL analysis.