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.
CVE-2026-74888
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-17. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 6%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 17, 2026
Advisory Details (2)
Auto-updated Aug 17, 2026openssl_encrypt before 1.4.0 Non-Standard PBKDF2 Key Derivation | Advisories | VulnCheck
https://www.vulncheck.com/advisories/openssl-encrypt-before-non-standard-pbkdf2-key-derivationCustom PBKDF2 loop uses iterations=1 per call — non-standard construction · Advisory · jahlives/openssl_encrypt · GitHub
https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-743f-89fg-x288Vendor Advisories for CVE-2026-74888(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 21× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 05:11 UTCEG score recompute
- 2026-08-21 05:11 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 16:47 UTCGHSA enrichment
- 2026-08-20 04:21 UTCEG score recompute
- 2026-08-20 04:21 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 15:56 UTCGHSA enrichment
- 2026-08-19 03:20 UTCGHSA enrichment
- 2026-08-18 14:56 UTCEG score recompute
- 2026-08-18 14:56 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 01:54 UTCGHSA enrichment
- 2026-08-17 13:30 UTCEG score recompute
- 2026-08-17 13:30 UTCGHSA enrichment
- 2026-08-17 12:56 UTCEG score recompute
- 2026-08-17 12:56 UTCGHSA enrichment
- 2026-08-17 11:39 UTCEG score recompute
- 2026-08-17 11:13 UTCEG score recompute
- 2026-08-17 11:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-327
Frequently asked(5)
What is CVE-2026-74888?
When was CVE-2026-74888 disclosed?
Is CVE-2026-74888 actively exploited?
What is the CVSS score of CVE-2026-74888?
How do I remediate CVE-2026-74888?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-74888
Is Your Infrastructure Affected by CVE-2026-74888?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.