CVE-2026-69102

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-11. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this week
9.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: 9.8Exploit: None knownExposed: 0

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

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.8(medium)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 14, 2026

Advisory Details (4)

Auto-updated Sep 18, 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
github_commit

commit 6cda394ec111 (dromara/MaxKey)

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

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

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

https://github.com/dromara/MaxKey/issues/270
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 44× in last 7d / 190× 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 275 total refreshes for this CVE.

  1. 2026-09-20 21:50 UTCEG score recompute
  2. 2026-09-20 21:50 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-20 17:25 UTCGHSA enrichment
  5. 2026-09-20 10:18 UTCGHSA enrichment
  6. 2026-09-20 05:55 UTCGHSA enrichment
  7. 2026-09-20 01:36 UTCGHSA enrichment
  8. 2026-09-19 21:17 UTCGHSA enrichment
  9. 2026-09-19 16:55 UTCEG score recompute
  10. 2026-09-19 16:55 UTCGHSA enrichment
  11. 2026-09-19 12:16 UTCGHSA enrichment
  12. 2026-09-19 07:05 UTCGHSA enrichment
  13. 2026-09-19 02:33 UTCGHSA enrichment
  14. 2026-09-18 22:13 UTCEG score recompute
  15. 2026-09-18 22:13 UTCGHSA enrichment
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-18 17:54 UTCGHSA enrichment
  18. 2026-09-18 13:34 UTCGHSA enrichment
  19. 2026-09-18 09:14 UTCGHSA enrichment
  20. 2026-09-18 04:55 UTCGHSA enrichment
  21. 2026-09-18 00:36 UTCEG score recompute
  22. 2026-09-18 00:36 UTCGHSA enrichment
  23. 2026-09-17 13:48 UTCGHSA enrichment
  24. 2026-09-17 09:05 UTCGHSA enrichment
  25. 2026-09-17 04:46 UTCGHSA enrichment
Show 75 more
  1. 2026-09-17 00:27 UTCEG score recompute
  2. 2026-09-17 00:26 UTCGHSA enrichment
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 11:08 UTCGHSA enrichment
  5. 2026-09-16 06:50 UTCEG score recompute
  6. 2026-09-16 06:49 UTCGHSA enrichment
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-16 02:30 UTCGHSA enrichment
  9. 2026-09-15 22:11 UTCGHSA enrichment
  10. 2026-09-15 13:20 UTCGHSA enrichment
  11. 2026-09-15 07:14 UTCEG score recompute
  12. 2026-09-15 07:14 UTCGHSA enrichment
  13. 2026-09-15 02:55 UTCGHSA enrichment
  14. 2026-09-14 22:35 UTCGHSA enrichment
  15. 2026-09-14 17:16 UTCGHSA enrichment
  16. 2026-09-14 12:57 UTCGHSA enrichment
  17. 2026-09-14 08:17 UTCGHSA enrichment
  18. 2026-09-14 03:58 UTCGHSA enrichment
  19. 2026-09-13 23:39 UTCGHSA enrichment
  20. 2026-09-13 19:20 UTCEG score recompute
  21. 2026-09-13 19:20 UTCGHSA enrichment
  22. 2026-09-13 14:59 UTCGHSA enrichment
  23. 2026-09-13 10:32 UTCGHSA enrichment
  24. 2026-09-13 06:11 UTCGHSA enrichment
  25. 2026-09-13 01:52 UTCGHSA enrichment
  26. 2026-09-12 21:33 UTCGHSA enrichment
  27. 2026-09-12 17:14 UTCEG score recompute
  28. 2026-09-12 17:14 UTCGHSA enrichment
  29. 2026-09-12 12:55 UTCGHSA enrichment
  30. 2026-09-12 08:35 UTCGHSA enrichment
  31. 2026-09-12 04:16 UTCGHSA enrichment
  32. 2026-09-11 23:57 UTCGHSA enrichment
  33. 2026-09-11 18:17 UTCEG score recompute
  34. 2026-09-11 18:17 UTCGHSA enrichment
  35. 2026-09-11 14:53 UTCEPSS rescore
  36. 2026-09-11 13:58 UTCEG score recompute
  37. 2026-09-11 13:58 UTCGHSA enrichment
  38. 2026-09-11 09:37 UTCEPSS rescore
  39. 2026-09-11 06:03 UTCGHSA enrichment
  40. 2026-09-11 01:43 UTCGHSA enrichment
  41. 2026-09-10 21:24 UTCEG score recompute
  42. 2026-09-10 21:24 UTCGHSA enrichment
  43. 2026-09-10 17:01 UTCGHSA enrichment
  44. 2026-09-10 12:34 UTCEG score recompute
  45. 2026-09-10 12:34 UTCGHSA enrichment
  46. 2026-09-10 06:18 UTCGHSA enrichment
  47. 2026-09-10 01:54 UTCGHSA enrichment
  48. 2026-09-09 17:58 UTCGHSA enrichment
  49. 2026-09-09 09:43 UTCGHSA enrichment
  50. 2026-09-09 05:24 UTCEG score recompute
  51. 2026-09-09 05:23 UTCGHSA enrichment
  52. 2026-09-08 22:01 UTCEPSS rescore
  53. 2026-09-08 07:11 UTCGHSA enrichment
  54. 2026-09-08 01:27 UTCGHSA enrichment
  55. 2026-09-07 21:07 UTCGHSA enrichment
  56. 2026-09-07 16:48 UTCEG score recompute
  57. 2026-09-07 16:48 UTCGHSA enrichment
  58. 2026-09-07 16:01 UTCEPSS rescore
  59. 2026-09-07 06:00 UTCGHSA enrichment
  60. 2026-09-07 01:26 UTCGHSA enrichment
  61. 2026-09-06 20:58 UTCGHSA enrichment
  62. 2026-09-06 16:39 UTCEG score recompute
  63. 2026-09-06 16:39 UTCGHSA enrichment
  64. 2026-09-06 13:47 UTCEPSS rescore
  65. 2026-09-06 12:20 UTCGHSA enrichment
  66. 2026-09-06 07:45 UTCGHSA enrichment
  67. 2026-09-06 03:24 UTCGHSA enrichment
  68. 2026-09-05 23:03 UTCGHSA enrichment
  69. 2026-09-05 18:44 UTCEG score recompute
  70. 2026-09-05 18:44 UTCGHSA enrichment
  71. 2026-09-05 15:31 UTCEPSS rescore
  72. 2026-09-05 14:25 UTCGHSA enrichment
  73. 2026-09-05 09:32 UTCGHSA enrichment
  74. 2026-09-05 05:13 UTCGHSA enrichment
  75. 2026-09-05 00:53 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 in the National Vulnerability Database on August 11, 2026, with the most recent update on August 14, 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% probability of exploitation in the next 30 days, which ranks it in the top 62.2% of all scored CVEs.
What is the CVSS score of CVE-2026-69102?
CVE-2026-69102 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-69102?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69102, 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-69102

Explore →

Is Your Infrastructure Affected by CVE-2026-69102?

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

Start Free Scan →Browse All CVEs