CVE-2026-67345: Permissive List of Allowed Inputs in dromara MaxKey
MaxKey through 4.1.12, fixed in commit ddbb72f, contains an insufficient redirect URI validation vulnerability in DefaultRedirectResolver.hostMatches() that allows remote attackers to hijack OAuth 2.0 authorization codes by supplying a crafted redirect_uri whose hostname suffix matches a registered URI without proper dot-boundary anchoring. Attackers who control a domain ending with the registered redirect URI hostname can social-engineer victims into clicking a crafted authorization URL, causing the authorization code to be issued to the attacker-controlled URI and exchanged for an access token granting access to the victim's identity.
AI Analysis
Technical Summary
CVE-2026-67345 affects dromara MaxKey through version 4.1.12. The vulnerability arises from insufficient validation of redirect URIs in the DefaultRedirectResolver.hostMatches() method. Specifically, the hostname suffix matching does not enforce proper dot-boundary anchoring, allowing an attacker who controls a domain with a hostname suffix matching a legitimate registered redirect URI to craft a malicious redirect_uri parameter. When a victim clicks on this crafted authorization URL, the OAuth 2.0 authorization code is issued to the attacker-controlled URI, enabling the attacker to exchange it for an access token and gain access to the victim's identity. This flaw compromises the OAuth 2.0 authorization flow's integrity.
Potential Impact
An attacker can hijack OAuth 2.0 authorization codes by exploiting the insufficient redirect URI validation, potentially gaining unauthorized access to victim identities via access tokens. This undermines the security of the OAuth 2.0 authorization process in affected MaxKey versions, leading to high-severity risks of identity compromise.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability is fixed in commit ddbb72f, so upgrading to a version including this commit or later is recommended once available. Until then, avoid using vulnerable versions or apply any official fixes provided by the vendor.
CVE-2026-67345: Permissive List of Allowed Inputs in dromara MaxKey
Description
MaxKey through 4.1.12, fixed in commit ddbb72f, contains an insufficient redirect URI validation vulnerability in DefaultRedirectResolver.hostMatches() that allows remote attackers to hijack OAuth 2.0 authorization codes by supplying a crafted redirect_uri whose hostname suffix matches a registered URI without proper dot-boundary anchoring. Attackers who control a domain ending with the registered redirect URI hostname can social-engineer victims into clicking a crafted authorization URL, causing the authorization code to be issued to the attacker-controlled URI and exchanged for an access token granting access to the victim's identity.
CVSS v4.0
Score 8.5high
Affected software
dromara
MaxKey
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-67345 affects dromara MaxKey through version 4.1.12. The vulnerability arises from insufficient validation of redirect URIs in the DefaultRedirectResolver.hostMatches() method. Specifically, the hostname suffix matching does not enforce proper dot-boundary anchoring, allowing an attacker who controls a domain with a hostname suffix matching a legitimate registered redirect URI to craft a malicious redirect_uri parameter. When a victim clicks on this crafted authorization URL, the OAuth 2.0 authorization code is issued to the attacker-controlled URI, enabling the attacker to exchange it for an access token and gain access to the victim's identity. This flaw compromises the OAuth 2.0 authorization flow's integrity.
Potential Impact
An attacker can hijack OAuth 2.0 authorization codes by exploiting the insufficient redirect URI validation, potentially gaining unauthorized access to victim identities via access tokens. This undermines the security of the OAuth 2.0 authorization process in affected MaxKey versions, leading to high-severity risks of identity compromise.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability is fixed in commit ddbb72f, so upgrading to a version including this commit or later is recommended once available. Until then, avoid using vulnerable versions or apply any official fixes provided by the vendor.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-29T13:09:45.993Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a6b8fab9c2644c7f8731757
Added to database: 07/30/2026, 17:53:47 UTC
Last enriched: 08/15/2026, 13:49:37 UTC
Last updated: 09/12/2026, 22:01:36 UTC
Views: 89
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.