Advisory record · GHSA-743f-89fg-x288

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 forma...

CVSS 8.7 HighEPSS 0.0027 · 19th percentile

Published by the GitHub Advisory Database at 17 Aug 2026, 11:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
openssl-encryptPyPI<1.4.01.4.0
Identifiers
GHSA-743f-89fg-x288 · CVE-2026-74888 · PYSEC-2026-3764
Weakness (CWE)
CWE-327
Published
17 Aug 2026
Updated
2 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The openssl-encrypt package, versions before 1.4.0, uses a non-standard key derivation method that runs PBKDF2 with one iteration per call inside an outer loop, and its security properties have not been formally analyzed. An attacker who has encrypted files from this package could crack the passwords protecting them more efficiently than with standard PBKDF2. Upgrade to version 1.4.0 or later, which is the listed fix. Files already encrypted with the old method remain weaker, so changing their passwords after upgrading is advisable.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.7 High 4.0 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 CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0027, the 19th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:38 UTC First seen by agentprime
  2. 31 Oct 2026, 14:38 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.