Insufficient Redirect URI Validation in MaxKey OAuth 2.0 Implementation
CVE-2026-67345

8.5HIGH

Key Information:

Vendor

Dromara

Status
Maxkey
Vendor
CVE Published:
30 July 2026

Badges

👾 Exploit Exists🟡 Public PoC

What is CVE-2026-67345?

The MaxKey authentication framework up to version 4.1.12 suffers from an insufficient redirect URI validation vulnerability in the DefaultRedirectResolver.hostMatches() method. This flaw allows attackers to hijack OAuth 2.0 authorization codes by manipulating the redirect_uri. If an attacker controls a domain that ends in the same hostname as a registered redirect URI, they can craft a malicious authorization URL. Victims unknowingly clicking this URL may have their authorization code sent to the attacker, allowing access to sensitive identity information. Developers must ensure proper dot-boundary anchoring in their URI validation to prevent such exploit scenarios.

Affected Version(s)

MaxKey 0 <= 4.1.12

MaxKey ddbb72fb24ab8e66aa422fb14b1177330bcffb45

Exploit Proof of Concept (PoC)

PoC code is written by security researchers to demonstrate the vulnerability can be exploited. PoC code is also a key component for weaponization which could lead to ransomware.

CVE-2026-67345 - Proof of Concept

References

https://github.com/dromara/MaxKey/issues/269
technical-descriptionexploit
https://github.com/dromara/MaxKey/commit/ddbb72fb24ab8e66...
patch
https://www.vulncheck.com/advisories/maxkey-defaultredire...
third-party-advisory

CVSS V4

Score:
8.5
Severity:
HIGH
Confidentiality:
High
Integrity:
High
Availability:
None
Attack Vector:
Network
Attack Complexity:
Low
Attack Required:
None
Privileges Required:
Undefined
User Interaction:
Unknown

Timeline

  • 🟡

    Public PoC available

  • 👾

    Exploit known to exist

  • Vulnerability published

  • Vulnerability Reserved

Credit

George Chen
.