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

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

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-m8xp-ww9g-3j6j

## 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 (DEPRECATED: Insufficient Session Expiration)

## 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.

## 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:

- PoC: Shiori JWT CheckToken never re-validates account state (CVE-2026-71206, High 8.2) (github_poc): https://github.com/Nel-droid/CVE-2026-71206-PoC

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71206 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-71206 in the wild and no public exploit code.

Affected product: go-shiori shiori. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71206/ (Markdown: https://insights.sbomify.com/CVE-2026-71206/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71206
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71206
- OSV: https://osv.dev/vulnerability/CVE-2026-71206

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71206/
Summaries are generated and may contain mistakes; the official description above is the record.