CVE-2026-69102

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-11. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

MaxKey contains an unauthorized access vulnerability due to a hard-coded JWT signing secret in application-maxkey.properties that allows unauthenticated attackers to forge valid JWT tokens and authenticate as any user by exploiting the password-skipped login endpoint. Attackers can craft a JWT token signed with the publicly known default secret, submit it to the /sign/login/jwt/trust endpoint, and obtain a fully authenticated admin session with access to SSO application configuration and downstream application secrets.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 11, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Oct 1, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

MaxKey Hard-coded JWT Secret Unauthorized Access via /login/jwt/trust | Advisories | VulnCheck

https://www.vulncheck.com/advisories/maxkey-hard-coded-jwt-secret-unauthorized-access-via-login-jwt-trust
generic

[Vulnerability] Unauthorized Access due to Hard-coded JWT secret · Issue #270 · dromara/MaxKey · GitHub

https://github.com/dromara/MaxKey/issues/270
github_commit

commit 6cda394ec111 (dromara/MaxKey)

Fix landed in dromara/MaxKey commit 6cda394ec111 — awaiting tagged release

https://github.com/dromara/MaxKey/commit/6cda394ec111f03a06fb2eed0de74f787d68bd97
generic

GitHub - dromara/MaxKey: Dromara MaxKey 🗝️ SSO ,Leading-Edge IAM-IDaas(Identity and Access Management) Product , Under Apache-2.0 is free ，业界领先的IAM-IDaas身份管理和认证产品，遵循Apache-2.0开源免费，支持OAuth2.x、OpenID Connect、SAML2.0、CAS、JWT、SCIM等SSO标准协议，基于RBAC统一权限控制，实现用户生命周期管理，开源、安全、合规、自主可控。 · GitHub

https://github.com/dromara/MaxKey

Vendor Advisories for CVE-2026-69102(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 30× in last 7d / 163× 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.

Showing the most recent 100 of 341 total refreshes for this CVE.

  1. 2026-10-05 07:39 UTCEG score recompute
  2. 2026-10-05 07:39 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 22:35 UTCGHSA enrichment
  5. 2026-10-04 13:23 UTCGHSA enrichment
  6. 2026-10-04 09:00 UTCGHSA enrichment
  7. 2026-10-04 04:14 UTCGHSA enrichment
  8. 2026-10-03 20:29 UTCEG score recompute
  9. 2026-10-03 20:29 UTCGHSA enrichment
  10. 2026-10-03 14:26 UTCEPSS rescore
  11. 2026-10-03 02:37 UTCGHSA enrichment
  12. 2026-10-02 22:18 UTCEG score recompute
  13. 2026-10-02 22:18 UTCGHSA enrichment
  14. 2026-10-02 17:56 UTCEPSS rescore
  15. 2026-10-02 16:19 UTCGHSA enrichment
  16. 2026-10-02 08:29 UTCEG score recompute
  17. 2026-10-02 08:29 UTCGHSA enrichment
  18. 2026-10-01 19:50 UTCEPSS rescore
  19. 2026-10-01 15:19 UTCGHSA enrichment
  20. 2026-10-01 11:01 UTCGHSA enrichment
  21. 2026-10-01 06:41 UTCGHSA enrichment
  22. 2026-10-01 02:22 UTCGHSA enrichment
  23. 2026-09-30 22:03 UTCEG score recompute
  24. 2026-09-30 22:03 UTCGHSA enrichment
  25. 2026-09-30 15:03 UTCEPSS rescore
Show 75 more
  1. 2026-09-29 05:01 UTCEG score recompute
  2. 2026-09-29 05:01 UTCGHSA enrichment
  3. 2026-09-28 15:24 UTCEG score recompute
  4. 2026-09-28 15:24 UTCGHSA enrichment
  5. 2026-09-28 13:52 UTCEPSS rescore
  6. 2026-09-28 10:49 UTCGHSA enrichment
  7. 2026-09-28 06:23 UTCGHSA enrichment
  8. 2026-09-28 02:04 UTCGHSA enrichment
  9. 2026-09-27 16:54 UTCEG score recompute
  10. 2026-09-27 16:54 UTCGHSA enrichment
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-27 10:01 UTCEG score recompute
  13. 2026-09-27 10:01 UTCGHSA enrichment
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-25 12:30 UTCGHSA enrichment
  16. 2026-09-25 08:05 UTCGHSA enrichment
  17. 2026-09-25 03:46 UTCGHSA enrichment
  18. 2026-09-24 20:35 UTCEG score recompute
  19. 2026-09-24 20:35 UTCGHSA enrichment
  20. 2026-09-24 09:55 UTCGHSA enrichment
  21. 2026-09-24 05:36 UTCGHSA enrichment
  22. 2026-09-24 01:16 UTCGHSA enrichment
  23. 2026-09-23 20:57 UTCEG score recompute
  24. 2026-09-23 20:57 UTCGHSA enrichment
  25. 2026-09-23 17:54 UTCEPSS rescore
  26. 2026-09-23 14:29 UTCGHSA enrichment
  27. 2026-09-23 10:08 UTCGHSA enrichment
  28. 2026-09-23 05:48 UTCGHSA enrichment
  29. 2026-09-23 01:29 UTCGHSA enrichment
  30. 2026-09-22 21:09 UTCEG score recompute
  31. 2026-09-22 21:09 UTCGHSA enrichment
  32. 2026-09-22 14:49 UTCGHSA enrichment
  33. 2026-09-22 10:01 UTCGHSA enrichment
  34. 2026-09-22 04:56 UTCGHSA enrichment
  35. 2026-09-22 00:37 UTCEG score recompute
  36. 2026-09-22 00:37 UTCGHSA enrichment
  37. 2026-09-21 21:09 UTCEPSS rescore
  38. 2026-09-21 20:17 UTCGHSA enrichment
  39. 2026-09-21 10:52 UTCGHSA enrichment
  40. 2026-09-21 06:33 UTCGHSA enrichment
  41. 2026-09-21 02:09 UTCGHSA enrichment
  42. 2026-09-20 21:50 UTCEG score recompute
  43. 2026-09-20 21:50 UTCGHSA enrichment
  44. 2026-09-20 20:16 UTCEPSS rescore
  45. 2026-09-20 17:25 UTCGHSA enrichment
  46. 2026-09-20 10:18 UTCGHSA enrichment
  47. 2026-09-20 05:55 UTCGHSA enrichment
  48. 2026-09-20 01:36 UTCGHSA enrichment
  49. 2026-09-19 21:17 UTCGHSA enrichment
  50. 2026-09-19 16:55 UTCEG score recompute
  51. 2026-09-19 16:55 UTCGHSA enrichment
  52. 2026-09-19 12:16 UTCGHSA enrichment
  53. 2026-09-19 07:05 UTCGHSA enrichment
  54. 2026-09-19 02:33 UTCGHSA enrichment
  55. 2026-09-18 22:13 UTCEG score recompute
  56. 2026-09-18 22:13 UTCGHSA enrichment
  57. 2026-09-18 19:28 UTCEPSS rescore
  58. 2026-09-18 17:54 UTCGHSA enrichment
  59. 2026-09-18 13:34 UTCGHSA enrichment
  60. 2026-09-18 09:14 UTCGHSA enrichment
  61. 2026-09-18 04:55 UTCGHSA enrichment
  62. 2026-09-18 00:36 UTCEG score recompute
  63. 2026-09-18 00:36 UTCGHSA enrichment
  64. 2026-09-17 13:48 UTCGHSA enrichment
  65. 2026-09-17 09:05 UTCGHSA enrichment
  66. 2026-09-17 04:46 UTCGHSA enrichment
  67. 2026-09-17 00:27 UTCEG score recompute
  68. 2026-09-17 00:26 UTCGHSA enrichment
  69. 2026-09-16 14:08 UTCEPSS rescore
  70. 2026-09-16 11:08 UTCGHSA enrichment
  71. 2026-09-16 06:50 UTCEG score recompute
  72. 2026-09-16 06:49 UTCGHSA enrichment
  73. 2026-09-16 05:15 UTCEPSS rescore
  74. 2026-09-16 02:30 UTCGHSA enrichment
  75. 2026-09-15 22:11 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-69102?
CVE-2026-69102 is a critical vulnerability published on August 11, 2026. MaxKey contains an unauthorized access vulnerability due to a hard-coded JWT signing secret in application-maxkey.properties that allows unauthenticated attackers to forge valid JWT tokens and authenticate as any user by exploiting the password-skipped login endpoint. Attackers can craft a JWT…
When was CVE-2026-69102 disclosed?
CVE-2026-69102 was first published on August 11, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69102 actively exploited?
CVE-2026-69102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69102?
CVE-2026-69102 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69102?
An upstream fix for CVE-2026-69102 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-69102 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-69102?

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

Book a Demo →Browse All CVEs