CVE-2026-71206 shiori - JWT CheckToken Never Re-Validates Account State, Allowing Stale-Privilege Access After Deletion or Demotion

High 8.2 Published Updated

Attackers retain access using stale JWTs after account deletion or demotion because Shiori fails to re-validate account state against the database.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-71206?

CVE-2026-71206 is a high-severity authentication bypass vulnerability in go-shiori shiori, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Shiori's CheckToken function (internal/domains/auth.go) validates only the JWT's HMAC signature and returns the embedded claims.Account object unmodified, never re-fetching the account from the database. No session store or token-revocation mechanism exists in the codebase.

Weakness: CWE-613

Which versions are affected by CVE-2026-71206?

How do I fix CVE-2026-71206?

No fix has been published for CVE-2026-71206 yet. Limit exposure of the affected software until one is available.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-71206 being exploited?

There is no known exploitation of CVE-2026-71206 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

Sources

Also known as GHSA-m8xp-ww9g-3j6j.

Is CVE-2026-71206 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free