Second-factor bypass via unchecked OIDC session state
Published Mar 12, 2026 · Updated Mar 12, 2026
Authentication bypass in Tinyauth before 5.0.3 allows remote authenticated users to obtain OIDC tokens without completing TOTP. The OIDC authorize handler accepts a populated user context and issues a code without checking IsLoggedIn or TotpPending, after which StoreCode binds it to the user's subject. Exploitation requires a known password, a TOTP-enabled local account, and at least one configured OIDC client; relying applications accept the resulting tokens.
Summary
What happened
Authentication bypass in Tinyauth before 5.0.3 allows remote authenticated users to obtain OIDC tokens without completing TOTP. The OIDC authorize handler accepts a populated user context and issues a code without checking IsLoggedIn or TotpPending, after which StoreCode binds it to the user's subject. Exploitation requires a known password, a TOTP-enabled local account, and at least one configured OIDC client; relying applications accept the resulting tokens.
The record
- CVE
- CVE-2026-32246
- Published
- Mar 12, 2026
- Updated
- Mar 12, 2026
- Vendor
- Tinyauth
- Product
- Tinyauth
- Classifications
- CWE-287, T1190
- 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.
Public exploit references
- TOTP-pending OIDC authorization-code 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