# CVE-2026-69102: MaxKey Hard-coded JWT Secret Unauthorized Access via /login/jwt/trust

> Attackers can forge JWT tokens using a hard-coded secret to gain unauthorized admin access to the MaxKey SSO system.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-xhfc-44v3-4rhf

## What is CVE-2026-69102?

CVE-2026-69102 is a critical vulnerability in dromara MaxKey, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2026-69102?


## How do I fix CVE-2026-69102?

No fix has been published for CVE-2026-69102 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-69102 being exploited?

There is no known exploitation of CVE-2026-69102 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-69102 and fix it if it is affected.

What it is: CVE-2026-69102 is a critical vulnerability in dromara MaxKey, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-69102 in the wild and no public exploit code.

Affected product: dromara MaxKey. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-69102/ (Markdown: https://insights.sbomify.com/CVE-2026-69102/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-69102
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-69102
- OSV: https://osv.dev/vulnerability/CVE-2026-69102

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-69102/
Summaries are generated and may contain mistakes; the official description above is the record.