CVE-2026-69102
Hard-coded JWT secret in MaxKey allows forging tokens to gain admin SSO access
Is CVE-2026-69102 being exploited?
Not confirmed. CVE-2026-69102 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.
How severe is CVE-2026-69102?
CVE-2026-69102 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-69102?
Not known from our data. No patch reference has been recorded for CVE-2026-69102, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-69102 affect?
CVE-2026-69102 affects MaxKey SSO, application-maxkey.properties (hard-coded JWT secret), /sign/login/jwt/trust endpoint. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-69102?
Replace hard-coded secret, disable JWT-trust endpoint, rotate keys, apply vendor patch when released
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can forge JWTs with the default secret, bypass login, obtain admin sessions, access SSO config and downstream application secrets.
Immediate action required
- affected<= 4.1.11
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.