Advisory record · GHSA-xg2q-62g2-cvcm

Tinyauth's OIDC authorization codes are not bound to client on token exchange

CVSS 6.5 MediumEPSS 0.0030 · 22nd percentile

Published by the GitHub Advisory Database at 12 Mar 2026, 16:38 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/steveiliop56/tinyauthGo<1.0.1-20260311144920-9eb2d33064b71.0.1-20260311144920-9eb2d33064b7
Identifiers
GHSA-xg2q-62g2-cvcm · CVE-2026-32245 · GO-2026-4689
Weakness (CWE)
CWE-863
Published
12 Mar 2026
Updated
24 Mar 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Tinyauth versions before 1.0.1-20260311144920-9eb2d33064b7 are affected. The token endpoint does not check that the client exchanging an authorization code is the client the code was issued to. An attacker who operates a second OIDC client on the same instance and can obtain another client's authorization code, for example from a leaked redirect URL or logs, can exchange it with their own credentials and receive tokens for a user who never authorized their application. Upgrade to 1.0.1-20260311144920-9eb2d33064b7 or later.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0030, the 22nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:08 UTC First seen by agentprime
  2. 31 Oct 2026, 15:08 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.