CVE-2026-74892

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: 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 hardcoded default secret key in the standalone telemetry server configuration that is used for API key hashing. Attackers who know this default value can predict or forge API key hashes to compromise telemetry API authentication.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
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 Hardcoded Secret Key | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openssl-encrypt-before-hardcoded-secret-key
github Patch Available

Hardcoded secret key in standalone telemetry server · Advisory · jahlives/openssl_encrypt · GitHub

https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-p926-6hjp-w9jw

Vendor Advisories for CVE-2026-74892(1)

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

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 01:48 UTCEG score recompute
  2. 2026-08-21 01:48 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 14:05 UTCGHSA enrichment
  5. 2026-08-20 02:23 UTCEG score recompute
  6. 2026-08-20 02:23 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 14:41 UTCGHSA enrichment
  9. 2026-08-19 03:00 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:04 UTCGHSA enrichment
  17. 2026-08-17 23:21 UTCEG score recompute
  18. 2026-08-17 23:21 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-74892?
CVE-2026-74892 is a high vulnerability published on August 17, 2026. openssl_encrypt versions before 1.4.0 contain a hardcoded default secret key in the standalone telemetry server configuration that is used for API key hashing. Attackers who know this default value can predict or forge API key hashes to compromise telemetry API authentication.
When was CVE-2026-74892 disclosed?
CVE-2026-74892 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-74892 actively exploited?
CVE-2026-74892 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 76.6% of all scored CVEs.
What is the CVSS score of CVE-2026-74892?
CVE-2026-74892 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-74892?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74892, 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

Explore the affected products and dependency analysis for CVE-2026-74892

Explore →

Is Your Infrastructure Affected by CVE-2026-74892?

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

Start Free Scan →Browse All CVEs