CVE-2026-74870

LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

Score 3.3 from GitHub Security Advisory (severity: HIGH) published 2026-08-17. The CNA's CVSS baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
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.3%CVSS: 3.3Exploit: None knownExposed services: Not assessed

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

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.3LOWmedium confidence
EG Risk
15
EG Risk 15/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 17, 2026

Last Modified

October 1, 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 rangeFix by version rangeDependents
openssl-encrypt0.2.2 ... 1.4.6 (51 versions)
  • every version up to 1.4.7: fixed in 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 / 44× 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-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 13:23 UTCEG score recompute
  3. 2026-10-04 13:23 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-01 19:50 UTCEPSS rescore
  6. 2026-10-01 15:30 UTCEG score recompute
  7. 2026-10-01 15:30 UTCGHSA enrichment
  8. 2026-09-30 10:04 UTCEG score recompute
  9. 2026-09-30 10:04 UTCGHSA enrichment
  10. 2026-09-29 15:24 UTCEPSS rescore
  11. 2026-09-28 13:52 UTCEPSS rescore
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-27 08:18 UTCEG score recompute
  14. 2026-09-27 08:18 UTCGHSA enrichment
  15. 2026-09-26 15:59 UTCEPSS rescore
  16. 2026-09-26 00:28 UTCEPSS rescore
  17. 2026-09-24 14:04 UTCEPSS rescore
  18. 2026-09-23 23:31 UTCEG score recompute
  19. 2026-09-23 23:31 UTCGHSA enrichment
  20. 2026-09-23 17:54 UTCEPSS rescore
  21. 2026-09-22 16:01 UTCEPSS rescore
  22. 2026-09-21 21:09 UTCEPSS rescore
  23. 2026-09-21 01:49 UTCEG score recompute
  24. 2026-09-21 01:49 UTCGHSA enrichment
  25. 2026-09-20 20:16 UTCEPSS rescore
Show 56 more
  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
  26. 2026-09-01 04:40 UTCEPSS rescore
  27. 2026-08-31 20:33 UTCEG score recompute
  28. 2026-08-31 20:33 UTCGHSA enrichment
  29. 2026-08-30 19:18 UTCEPSS rescore
  30. 2026-08-30 19:17 UTCEPSS rescore
  31. 2026-08-30 01:22 UTCEPSS rescore
  32. 2026-08-29 06:32 UTCEG score recompute
  33. 2026-08-29 06:31 UTCGHSA enrichment
  34. 2026-08-28 21:42 UTCEPSS rescore
  35. 2026-08-27 14:25 UTCEPSS rescore
  36. 2026-08-26 14:47 UTCEPSS rescore
  37. 2026-08-26 09:01 UTCEG score recompute
  38. 2026-08-26 09:01 UTCGHSA enrichment
  39. 2026-08-25 13:49 UTCEPSS rescore
  40. 2026-08-24 14:18 UTCEPSS rescore
  41. 2026-08-23 11:31 UTCEG score recompute
  42. 2026-08-23 11:31 UTCGHSA enrichment
  43. 2026-08-21 23:49 UTCEPSS rescore
  44. 2026-08-20 22:56 UTCEPSS rescore
  45. 2026-08-20 14:02 UTCEG score recompute
  46. 2026-08-20 14:02 UTCGHSA enrichment
  47. 2026-08-19 17:04 UTCEPSS rescore
  48. 2026-08-18 13:49 UTCEPSS rescore
  49. 2026-08-18 13:49 UTCEPSS rescore
  50. 2026-08-17 16:23 UTCEG score recompute
  51. 2026-08-17 16:23 UTCGHSA enrichment
  52. 2026-08-17 16:10 UTCEG score recompute
  53. 2026-08-17 16:10 UTCGHSA enrichment
  54. 2026-08-17 11:40 UTCEG score recompute
  55. 2026-08-17 11:13 UTCEG score recompute
  56. 2026-08-17 11:12 UTCMITRE cvelistV5first tracked

Related CVEs(same product + 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 on August 17, 2026, with the most recent update on October 1, 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.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74870?
CVE-2026-74870 has a CVSS base score of 3.3 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-74870?
No fix for CVE-2026-74870 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-74870 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs