CVE-2026-74893

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 hardcoded default JWT signing secrets in config.py that pass validation checks. Attackers with access to source code can forge valid JWT tokens for any client_id to gain authenticated access to keyserver and telemetry APIs.

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 17, 2026

Advisory Details (2)

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

openssl_encrypt before 1.4.0 JWT Token Forgery via Hardcoded Secrets | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openssl-encrypt-before-jwt-token-forgery-via-hardcoded-secrets
github Patch Available

Hardcoded default JWT secrets pass validation and enable token forgery · Advisory · jahlives/openssl_encrypt · GitHub

https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-qc6h-gfjh-7qqg

Vendor Advisories for CVE-2026-74893(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 20× in last 7d / 20× 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-20 22:56 UTCEPSS rescore
  2. 2026-08-20 22:53 UTCGHSA enrichment
  3. 2026-08-20 11:17 UTCGHSA enrichment
  4. 2026-08-19 23:41 UTCEG score recompute
  5. 2026-08-19 23:41 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 12:04 UTCGHSA enrichment
  8. 2026-08-19 00:28 UTCEG score recompute
  9. 2026-08-19 00:27 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 12:47 UTCGHSA enrichment
  13. 2026-08-18 01:10 UTCGHSA enrichment
  14. 2026-08-17 13:30 UTCEG score recompute
  15. 2026-08-17 13:30 UTCGHSA enrichment
  16. 2026-08-17 12:56 UTCEG score recompute
  17. 2026-08-17 12:56 UTCGHSA enrichment
  18. 2026-08-17 11:39 UTCEG score recompute
  19. 2026-08-17 11:13 UTCEG score recompute
  20. 2026-08-17 11:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74893?
CVE-2026-74893 is a high vulnerability published on August 17, 2026. opensslencrypt versions before 1.4.0 contain hardcoded default JWT signing secrets in config.py that pass validation checks. Attackers with access to source code can forge valid JWT tokens for any clientid to gain authenticated access to keyserver and telemetry APIs.
When was CVE-2026-74893 disclosed?
CVE-2026-74893 was first published in the National Vulnerability Database on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74893 actively exploited?
CVE-2026-74893 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-74893?
CVE-2026-74893 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-74893?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74893, 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-74893

Explore →

Is Your Infrastructure Affected by CVE-2026-74893?

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

Start Free Scan →Browse All CVEs