CVE-2026-69102: MaxKey Hard-coded JWT Secret Unauthorized Access via /login/jwt/trust
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
In application-maxkey.properties, change the hard-coded JWT signing secret used for JWT token verification to a unique secret value that is not publicly known.
MaxKey application-maxkey.properties (hard-coded JWT signing secret) = remove/replace the publicly known default secret with a unique, secret value - Compensating control
Block or restrict unauthenticated access to the /login/jwt/trust endpoint at the network layer (e.g., firewall/ingress) so forged JWT tokens cannot be submitted to obtain an authenticated admin session.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-69102?
CVE-2026-69102 has a critical severity rating of 9.8.
How do I fix CVE-2026-69102?
To fix CVE-2026-69102, update your MaxKey configuration to use a secure and unique JWT signing secret instead of the hard-coded one.
What kind of vulnerability is CVE-2026-69102?
CVE-2026-69102 is an unauthorized access vulnerability due to the hard-coded JWT signing secret.
What can attackers do with CVE-2026-69102?
Attackers can exploit CVE-2026-69102 to forge valid JWT tokens and authenticate as any user through the password-skipped login endpoint.
Which software is affected by CVE-2026-69102?
CVE-2026-69102 affects the MaxKey application.