CVE-2026-74870

LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: None knownExposed: 0

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

openssl_encrypt (pip) versions <= 1.4.7 contain an information exposure vulnerability where the 'hsm fido2-test' and 'hsm onlykey-test' diagnostic commands unconditionally print the full derived hardware pepper as hex to stdout/stderr (crypt_cli.py, handle_hsm_command). The printed value can persist in terminal scrollback, session recordings, or CI logs. Impact is limited because the pepper is derived from a random per-invocation test salt and is salt-bound, so the leaked value cannot be used to decrypt real files. A related plugin issue logged raw prf_data outside the secret-redaction path. Fixed in 1.4.8 (and 1.5.0) by removing the hex dumps and routing plugin debug output through the redaction layer.

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

Published

August 17, 2026

Last Modified

September 3, 2026

References (2)

Vendor Advisories for CVE-2026-74870(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.6 (51 versions)1.4.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 46× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 03:48 UTCEG score recompute
  3. 2026-09-18 03:48 UTCGHSA enrichment
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 06:18 UTCEG score recompute
  7. 2026-09-15 06:18 UTCGHSA enrichment
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-12 15:02 UTCEPSS rescore
  10. 2026-09-12 08:46 UTCEG score recompute
  11. 2026-09-12 08:46 UTCGHSA enrichment
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-10 09:35 UTCEPSS rescore
  14. 2026-09-09 11:16 UTCEG score recompute
  15. 2026-09-09 11:16 UTCGHSA enrichment
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-06 13:48 UTCEPSS rescore
  18. 2026-09-06 13:47 UTCEG score recompute
  19. 2026-09-06 13:47 UTCGHSA enrichment
  20. 2026-09-04 05:07 UTCEPSS rescore
  21. 2026-09-03 16:18 UTCEG score recompute
  22. 2026-09-03 16:18 UTCGHSA enrichment
  23. 2026-09-02 14:12 UTCEPSS rescore
  24. 2026-09-01 13:54 UTCEPSS rescore
  25. 2026-09-01 04:40 UTCEPSS rescore
Show 31 more
  1. 2026-09-01 04:40 UTCEPSS rescore
  2. 2026-08-31 20:33 UTCEG score recompute
  3. 2026-08-31 20:33 UTCGHSA enrichment
  4. 2026-08-30 19:18 UTCEPSS rescore
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-29 06:32 UTCEG score recompute
  8. 2026-08-29 06:31 UTCGHSA enrichment
  9. 2026-08-28 21:42 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 14:47 UTCEPSS rescore
  12. 2026-08-26 09:01 UTCEG score recompute
  13. 2026-08-26 09:01 UTCGHSA enrichment
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-24 14:18 UTCEPSS rescore
  16. 2026-08-23 11:31 UTCEG score recompute
  17. 2026-08-23 11:31 UTCGHSA enrichment
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-20 22:56 UTCEPSS rescore
  20. 2026-08-20 14:02 UTCEG score recompute
  21. 2026-08-20 14:02 UTCGHSA enrichment
  22. 2026-08-19 17:04 UTCEPSS rescore
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-18 13:49 UTCEPSS rescore
  25. 2026-08-17 16:23 UTCEG score recompute
  26. 2026-08-17 16:23 UTCGHSA enrichment
  27. 2026-08-17 16:10 UTCEG score recompute
  28. 2026-08-17 16:10 UTCGHSA enrichment
  29. 2026-08-17 11:40 UTCEG score recompute
  30. 2026-08-17 11:13 UTCEG score recompute
  31. 2026-08-17 11:12 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-74870?
CVE-2026-74870 is a low vulnerability published on August 17, 2026. opensslencrypt (pip) versions <= 1.4.7 contain an information exposure vulnerability where the 'hsm fido2-test' and 'hsm onlykey-test' diagnostic commands unconditionally print the full derived hardware pepper as hex to stdout/stderr (cryptcli.py, handlehsmcommand). The printed value can persist in…
When was CVE-2026-74870 disclosed?
CVE-2026-74870 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74870 actively exploited?
CVE-2026-74870 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 91.3% of all scored CVEs.
What is the CVSS score of CVE-2026-74870?
CVE-2026-74870 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-74870?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74870, 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-74870

Explore →

Is Your Infrastructure Affected by CVE-2026-74870?

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

Start Free Scan →Browse All CVEs