# CVE-2026-57574: Misskey: TOTP tokens can be reused

> Attackers can reuse TOTP codes to bypass two-factor authentication and take over user accounts in Misskey.

- **Severity:** High 7.4 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-2m5x-5mp6-6vpq

## What is CVE-2026-57574?

CVE-2026-57574 is a high-severity authentication bypass vulnerability in misskey-dev misskey, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Misskey is an open source, federated social media platform. Prior to 2026.6.0, Misskey contains a vulnerability in Time-based One-Time Password (TOTP) authentication in UserAuthService where insufficient validation of used tokens allows the reuse of a single-use code within its valid time step. If both credentials and a TOTP code are obtained concurrently, an attacker may reuse the code to perform unauthorized actions, potentially leading to account takeover. This issue is fixed in version 2026.6.0.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2026-57574?


## How do I fix CVE-2026-57574?

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

## Is CVE-2026-57574 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57574 is a high-severity authentication bypass vulnerability in misskey-dev misskey, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-57574 in the wild and no public exploit code.

Affected product: misskey-dev misskey. 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-57574/ (Markdown: https://insights.sbomify.com/CVE-2026-57574/index.md)
```

## Sources

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

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