openssl_encrypt versions before 1.4.6 contain a key derivation flaw in sequential XOR composition mode where the last stage cancels out during key generation. When configured with a single KDF and no prior hashing stage, attackers can bypass memory-hard key derivation and perform offline password cracking at SHA-256 speed instead of the configured KDF cost.
CVE-2026-74871
Score 6.2 from GitHub Security Advisory published 2026-08-17. a secondary CVSS source baseline 6.2; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.2
- EG Score
- 6.2(high)
- EG Risk
- 28(Track)EG Risk 28/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 computedSeverity62% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 17, 2026
Advisory Details (2)
Auto-updated Aug 17, 2026openssl_encrypt before 1.4.6 KDF Bypass via Sequential-XOR | Advisories | VulnCheck
https://www.vulncheck.com/advisories/openssl-encrypt-before-kdf-bypass-via-sequential-xorSequential-XOR last-stage cancellation bypasses KDF cost (memory-hard hashing defeated for --xor files) · Advisory · jahlives/openssl_encrypt · GitHub
https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-vxf9-vwp6-2w43Vendor Advisories for CVE-2026-74871(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 16× in last 7d / 16× 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-20 22:56 UTCEPSS rescore
- 2026-08-20 14:02 UTCEG score recompute
- 2026-08-20 14:02 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 15:20 UTCGHSA enrichment
- 2026-08-18 16:59 UTCEG score recompute
- 2026-08-18 16:59 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 18:31 UTCEG score recompute
- 2026-08-17 18:31 UTCGHSA enrichment
- 2026-08-17 17:48 UTCEG score recompute
- 2026-08-17 17:47 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
Frequently asked(5)
What is CVE-2026-74871?
When was CVE-2026-74871 disclosed?
Is CVE-2026-74871 actively exploited?
What is the CVSS score of CVE-2026-74871?
How do I remediate CVE-2026-74871?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-74871
Is Your Infrastructure Affected by CVE-2026-74871?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.