OAuth authorization code theft via suffix-matched redirects
Published Jul 30, 2026 · Updated Jul 30, 2026
Redirect URI validation in Dromara MaxKey 4.1.12 and earlier allows remote attackers to steal OAuth 2.0 authorization codes. DefaultRedirectResolver.hostMatches() accepts a requested hostname whenever it ends with the registered hostname, without requiring equality or a dot boundary. Exploitation requires control of a suffix-matching domain and victim interaction with a crafted authorization URL; the stolen code can be exchanged for an access token to the victim's connected account.
Summary
What happened
Redirect URI validation in Dromara MaxKey 4.1.12 and earlier allows remote attackers to steal OAuth 2.0 authorization codes. DefaultRedirectResolver.hostMatches() accepts a requested hostname whenever it ends with the registered hostname, without requiring equality or a dot boundary. Exploitation requires control of a suffix-matching domain and victim interaction with a crafted authorization URL; the stolen code can be exchanged for an access token to the victim's connected account.
The record
- CVE
- CVE-2026-67345
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- Dromara
- Product
- MaxKey
- Classifications
- CWE-183, T1528, T1566.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.1.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- MaxKey OAuth 2.0 redirect URI bypass proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo