Cross-client impersonation via unbound authorization codes
Published Mar 12, 2026 · Updated Mar 12, 2026
Incorrect authorization in Tinyauth before 5.0.3 allows remote authenticated users to impersonate users across OIDC clients. The token handler retrieves an authorization-code entry and validates its redirect URI, but fails to compare the stored client ID with the authenticated requesting client's ID before issuing tokens. Exploitation requires multiple configured clients and access to another client's authorization code; single-client deployments are unaffected.
Summary
What happened
Incorrect authorization in Tinyauth before 5.0.3 allows remote authenticated users to impersonate users across OIDC clients. The token handler retrieves an authorization-code entry and validates its redirect URI, but fails to compare the stored client ID with the authenticated requesting client's ID before issuing tokens. Exploitation requires multiple configured clients and access to another client's authorization code; single-client deployments are unaffected.
The record
- CVE
- CVE-2026-32245
- Published
- Mar 12, 2026
- Updated
- Mar 12, 2026
- Vendor
- Tinyauth
- Product
- Tinyauth
- Classifications
- CWE-863, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 12, 2026CVE publishedPublication date reported by the CVE source.
- Mar 12, 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=< 5.0.3
What conditions does exploitation require?
What is affected?
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
- Upstream cross-client authorization-code exchange proof of conceptproof of concept · 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