CVE-2026-32245

What it is

Tinyauth is an authentication and authorization server. Prior to 5.0.3, the OIDC token endpoint does not verify that the client exchanging an authorization code is the same client the code was issued to. A malicious OIDC client operator can exchange another client's authorization code using their own client credentials, obtaining tokens for users who never authorized their application. This violates RFC 6749 Section 4.1.3. This vulnerability is fixed in 5.0.3.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account, but needs a user to act. High risk of data tampering.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-03-12 19:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 10:35 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 6.5 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-03-12 19:16 UTC

Last modified

2026-06-17 10:35 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-863 · Incorrect authorization

Record status

Analyzed

Affected

• Tinyauth ≤ 5.0.2

Attack profile CVSS 3.1 · 6.5

Attack vector

Network

Complexity

High

Privileges needed

Low

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-32245.md and follow it. Check whether this project is affected by CVE-2026-32245. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge