Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-69102 – Authentication Bypass via Hard-coded JWT Secret – Dromara MaxKey ≤ 4.1.11

Be the first to know when new zero-days emerge:

Summary

CVE-2026-69102 is a critical authentication bypass vulnerability in Dromara MaxKey, an open-source identity and access management/SSO platform. The flaw stems from a hard-coded JWT signing secret shipped in the application’s default configuration, allowing an unauthenticated remote attacker to forge trusted authentication tokens and obtain a fully authenticated administrative session. The issue carries a CVSS v4.0 base score of 9.3 (Critical) and a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: MaxKey ships with a static, publicly-known JWT signing secret hard-coded in application-maxkey.properties. This secret is used to validate tokens submitted to the /sign/login/jwt/trust endpoint.
  • Trigger conditions: Any MaxKey deployment that has not overridden the default secret is exploitable. The trust-login flow (HttpJwtEntryPoint.java / AuthJwtService.java / TrustedAuthenticationProvider.java) verifies only the JWT signature and the sub (subject) claim, without validating issuer/audience claims or requiring a password.
  • Attack vector: Network-based, no authentication or user interaction required. An attacker crafts a JWT (e.g., with "sub":"admin") signed with the known default secret and submits it to the trust-login endpoint.
  • Impact: Successful exploitation grants the attacker a fully authenticated, admin-level session, exposing SSO application configurations and downstream federated application credentials/secrets — a complete compromise of confidentiality, integrity, and availability for the affected instance and any connected relying applications.
  • Weakness class: CWE-798 (Use of Hard-coded Credentials).

Affected software

  • Dromara MaxKey versions 0 through 4.1.11 (inclusive) — i.e., all releases up to and including 4.1.11 that use the default/unmodified JWT trust secret.

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 Base Score: 9.3 (Critical) — 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

Mitigation and recommended actions

  • Immediate: Upgrade to a MaxKey version that incorporates the fix delivered in commit 6cda394ec111f03a06fb2eed0de74f787d68bd97, which removes the shipped default JWT trust secret.
  • If unable to patch immediately:
    • Rotate/replace the default JWT signing secret in application-maxkey.properties with a strong, randomly generated, per-instance value.
    • Restrict or disable the /sign/login/jwt/trust endpoint if the JWT trust-login feature is not required.
    • Enforce validation of issuer (iss) and audience (aud) claims in addition to signature checks where custom configuration allows it.
    • Monitor authentication logs for unexpected admin sessions originating from the trust-login endpoint and audit SSO application configurations for unauthorized changes.
    • Restrict network exposure of the MaxKey management/authentication endpoints to trusted networks where possible.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge