Advisory record · GHSA-hvc7-763r-4f3h

openssl-encrypt has no owner verification on key revocation — any client can revoke any key

CVSS 8.7 HighEPSS 0.0045 · 39th percentile

Published by the GitHub Advisory Database at 1 Apr 2026, 21:11 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-hvc7-763r-4f3h · CVE-2026-74877 · PYSEC-2026-3743
Weakness (CWE)
CWE-639 · CWE-862
Published
1 Apr 2026
Updated
1 Sept 2026

Machine-written summary

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

The openssl-encrypt package before 1.4.0 has a key revocation method that does not check whether the requesting client owns the key. An authenticated client could therefore attempt to revoke another client's key, though the source notes that a valid revocation signature is still required. Upgrade to openssl-encrypt 1.4.0 or later.

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:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0045, the 39th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:39 UTC First seen by agentprime
  2. 31 Oct 2026, 14:39 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.