Skip to content
Fencer Intel
medium 6.5

CVE-2026-32245 json

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

published 7mo ago modified 4mo ago also GHSA-xg2q-62g2-cvcm , GO-2026-4689 , EUVD-2026-11679

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 22%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/steveiliop56/tinyauth 1.0.1-20260311144920-9eb2d33064b7
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20260317T205859-150000.1.152.1

suse advisories SUSE-SU-2026:1042-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Is CVE-2026-32245 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
7mo ago

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/steveiliop56/tinyauth/security/advisories/GHSA-xg2q-62g2-cvcm referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:H/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/steveiliop56/tinyauth
<1.0.1-20260311144920-9eb2d33064b7
all versions
1.0.1-20260311144920-9eb2d33064b7

Affected products

  • steveiliop56 tinyauth

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.