Quick answers
- Is CVE-2026-69102 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-69102 being exploited in the wild.
- How severe is CVE-2026-69102?
- Critical severity, with a CVSS score of 9.8, published 11 August 2026.
- Which products and versions are affected?
- Dromara MaxKey <UNKNOWN>.
- Is there a fix for CVE-2026-69102?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-69102 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-69102?
- Check whether you run Dromara MaxKey at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
MaxKey contains a hard-coded JWT signing secret in application-maxkey.properties that is publicly known. The vulnerability resides in the password-skipped login endpoint (/sign/login/jwt/trust), which accepts JWT tokens signed with this default secret without verifying their legitimacy. An unauthenticated attacker can craft a malicious JWT token using the publicly disclosed secret, submit it to the endpoint, and obtain a fully authenticated admin session. This grants complete access to SSO application configuration, user management, and all downstream application secrets. The vulnerability has been patched in a subsequent commit to the GitHub repository.
Affected products
- Dromara MaxKey <UNKNOWN>
Timeline
- 2026-08-11: disclosed