CVE-2026-74877

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-17. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

openssl_encrypt versions before 1.4.0 contain a missing ownership verification vulnerability in the revoke_key method that allows authenticated clients to revoke any other client's key. Attackers can revoke arbitrary keys by providing a valid ML-DSA signature, bypassing the intended ownership restriction.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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 computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

August 17, 2026

Last Modified

August 18, 2026

Advisory Details (2)

Auto-updated Aug 17, 2026
Patch available. Sources: github.
generic

openssl_encrypt before 1.4.0 Missing Ownership Verification via revoke_key | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openssl-encrypt-before-missing-ownership-verification-via-revoke-key
github Patch Available

No owner verification on key revocation — any client can revoke any key · Advisory · jahlives/openssl_encrypt · GitHub

https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-hvc7-763r-4f3h

Vendor Advisories for CVE-2026-74877(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
openssl-encrypt0.2.2 ... 1.4.0b8 (44 versions)1.4.0—

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.

  1. 2026-08-21 02:07 UTCEG score recompute
  2. 2026-08-21 02:07 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 14:22 UTCGHSA enrichment
  5. 2026-08-20 02:37 UTCEG score recompute
  6. 2026-08-20 02:37 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 14:50 UTCGHSA enrichment
  9. 2026-08-19 03:06 UTCGHSA enrichment
  10. 2026-08-18 15:18 UTCEG score recompute
  11. 2026-08-18 15:18 UTCGHSA enrichment
  12. 2026-08-18 14:51 UTCEG score recompute
  13. 2026-08-18 14:51 UTCGHSA enrichment
  14. 2026-08-18 13:49 UTCEPSS rescore
  15. 2026-08-18 13:49 UTCEPSS rescore
  16. 2026-08-18 11:11 UTCGHSA enrichment
  17. 2026-08-17 23:24 UTCEG score recompute
  18. 2026-08-17 23:24 UTCGHSA enrichment
  19. 2026-08-17 11:39 UTCEG score recompute
  20. 2026-08-17 11:13 UTCEG score recompute
  21. 2026-08-17 11:12 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-74877?
CVE-2026-74877 is a high vulnerability published on August 17, 2026. opensslencrypt versions before 1.4.0 contain a missing ownership verification vulnerability in the revokekey method that allows authenticated clients to revoke any other client's key. Attackers can revoke arbitrary keys by providing a valid ML-DSA signature, bypassing the intended ownership…
When was CVE-2026-74877 disclosed?
CVE-2026-74877 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74877 actively exploited?
CVE-2026-74877 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.9% of all scored CVEs.
What is the CVSS score of CVE-2026-74877?
CVE-2026-74877 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-74877?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74877, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-74877

Explore →

Is Your Infrastructure Affected by CVE-2026-74877?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs