Skip to main content
VulnerabilityPublished Updated

CVE-2026-33544: steveiliop56 tinyauth · Race Condition

Affects steveiliop56 tinyauthSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 5.0.5 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.0.5
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade tinyauth and steveiliop56/tinyauth to 5.0.5.

Affected software

ProductAffectedFixed in
steveiliop56tinyauthAffected
  • <5.0.5
Fixed in
  • 5.0.5
GitHubsteveiliop56/tinyauthpkg:github/steveiliop56/tinyauthOther threatsAffected
  • <5.0.5
Fixed in
  • 5.0.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade tinyauth to version 5.0.5 or later, where this race condition vulnerability has been patched. No other mitigation is required as the fix is available and official.

Description

Tinyauth is an authentication and authorization server. Prior to version 5.0.5, all three OAuth service implementations (GenericOAuthService, GithubOAuthService, GoogleOAuthService) store PKCE verifiers and access tokens as mutable struct fields on singleton instances shared across all concurrent requests. When two users initiate OAuth login for the same provider concurrently, a race condition between VerifyCode() and Userinfo() causes one user to receive a session with the other user's identity. This issue has been patched in version 5.0.5.

References

Community reviews

Loading reviews…