Skip to main content

Misskey EUVDEUVD-2026-43041

| CVE-2026-57574 HIGH
Authentication Bypass by Capture-replay (CWE-294)
2026-07-10 GitHub_M
7.4
CVSS 4.0 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Phish or AitM-proxy victim login
  2. Delivery
    Capture password and live TOTP code
  3. Exploit
    Replay same TOTP within time step
  4. Execution
    Bypass single-use 2FA check
  5. Persist
    Establish authenticated session
  6. Impact
    Take over account

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Replay attack prevention
Exploitation Conditions

Exploitation requires the attacker to obtain the victim's password AND a valid TOTP code for the same account concurrently (e.g., via phishing, a reverse-proxy AitM kit, or interception), then replay that code within its single valid TOTP time step (~30 seconds) before it naturally expires. The vulnerability only affects accounts that have TOTP two-factor authentication enabled on Misskey instances running a version prior to 2026.6.0. Limiting factors: the attacker cannot succeed with credentials alone or a code alone - both must be captured together and used within the short window (CVSS AC:H, AT:P, UI:A), making this suited to targeted or real-time AitM attacks rather than broad automated exploitation; accounts not using TOTP, or instances already on 2026.6.0, are not exploitable via this flaw.

Impact

The vendor CVSS 4.0 base score is 7.4 (High) with vector AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N, and the signals are internally consistent with a real but conditional threat. Network reachability (AV:N) and no required attacker privileges (PR:N) raise exposure, but High attack complexity (AC:H), a Present attack requirement (AT:P), and Active user interaction (UI:A) all reflect that success depends on the attacker first obtaining both the victim's credentials and a live TOTP code in the same short window - a meaningful barrier that pushes this toward opportunistic/targeted use rather than mass exploitation. Impact is credible: high confidentiality and integrity (VC:H/VI:H) with no availability impact (VA:N), consistent with account takeover. No EPSS score, KEV listing, or POC was provided in the intelligence, so exploitation-probability data is missing rather than low - the score reflects a real 2FA weakening, not a high-CVSS-but-trivial issue, but the replay-only nature and the requirement to already hold the password materially cap real-world urgency compared to a pre-auth RCE.

Exploit ScenarioDerived

An attacker who has phished or intercepted a Misskey user's username, password, and the TOTP code they just entered (for example via a man-in-the-middle proxy or a malicious login page) replays that same still-valid 6-digit code against the login endpoint before the ~30-second time step expires. Because the code was not invalidated on first use, the second authentication succeeds and the attacker gains an authenticated session, enabling account takeover. No public POC was provided, and the High attack complexity reflects the need to capture both factors concurrently.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 10, 2026

Authentication replay in Misskey before 2026.6.0 lets an attacker reuse a valid TOTP code that should be single-use, because UserAuthService fails to invalidate a code after its first successful use within the same time step. An adversary who concurrently captures a victim's password and one TOTP value can replay that code to authenticate, enabling unauthorized actions up to account takeover. No public exploit has been identified at time of analysis and it is not listed in CISA KEV; the vendor fixed the flaw in release 2026.6.0.

RemediationAI

Vendor-released patch: upgrade to Misskey 2026.6.0, which enforces single-use TOTP validation in UserAuthService; the fix corresponds to commits 00c6210a591db2b0be438740d05b82070fa68ac6 and d323fe00d04ac46ab0b4e66fce9169effaa8dfb7. Consult the advisory at https://github.com/misskey-dev/misskey/security/advisories/GHSA-2m5x-5mp6-6vpq and deploy from https://github.com/misskey-dev/misskey/releases/tag/2026.6.0. If an immediate upgrade is not possible, reduce the concurrent-capture window by encouraging or enforcing credential resets and, where supported, prefer FIDO2/WebAuthn passkeys over TOTP for privileged accounts since replay does not apply to challenge-response hardware factors; also monitor authentication logs for repeated use of the same OTP value or multiple logins from one code as a detection compensating control. These controls narrow but do not eliminate the replay window, so patching remains the definitive fix.

Affected VersionsENISA

misskey < 2026.6.0

Affected Packages

euvd misskey fix: 2026.6.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Misskey is an open-source, ActivePub-federated social media platform (fediverse) written primarily in TypeScript/Node.js. The flaw sits in its second-factor authentication path (UserAuthService), which validates Time-based One-Time Passwords (TOTP, RFC 6238). Correct TOTP implementations must mark a code as consumed after a successful verification so it cannot be accepted again during the ~30-second window in which it remains cryptographically valid. Here that used-token tracking is insufficient, so the same 6-digit code passes verification more than once. This maps to CWE-294 (Authentication Bypass by Capture-Replay): the security property being violated is single-use enforcement, not the OTP cryptography itself. The affected component is identified by CPE cpe:2.3:a:misskey-dev:misskey:*:*:*:*:*:*:*:* covering all versions prior to the patched 2026.6.0.

Know when Misskey gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 7.4 HIGH
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
vuln.today AI 6.8 MEDIUM

Network replay against the login endpoint (AV:N, PR:N) but success requires concurrently capturing password and a live TOTP within one time step (AC:H) and relies on the victim's active authentication (UI:R); takeover yields C:H/I:H, no availability impact.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
4.0 AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
High
Attack Requirements
Present
Privileges Required
None
User Interaction
Active
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
Patch available
Jul 10, 2026 - 22:02 EUVD

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Misskey's authentication service fails to invalidate TOTP codes after first use, allowing attackers who capture a user's password and one authentication code to replay that code for account access-a complete authentication bypass. Organizations running Misskey face immediate risk of account compromise and unauthorized access to platform data and functionality if the vulnerability is exploited.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 74% exploitable
Prevalence
Low
niche self-hosted federated fediverse platform, no enterprise footprint
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

37
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +37
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2024-32983 HIGH POC
7.5 Jun 03

Misskey is an open source, decentralized microblogging platform. Rated high severity (CVSS 7.5), this vulnerability is r

CVE-2025-66402 HIGH POC
7.1 Dec 16

Missing authorization checks in Misskey's favorites and clips export feature allow any authenticated user to read the co

CVE-2025-66482 MEDIUM POC
6.9 Dec 16

Login rate-limit bypass in Misskey (versions 2025.9.1 through 2025.11.x, and up to but not including 2025.12.0-alpha.2)

CVE-2019-1020010 MEDIUM POC
6.1 Jul 29

Misskey before 10.102.4 allows hijacking a user's token. Rated medium severity (CVSS 6.1), this vulnerability is remotel

CVE-2023-24812 CRITICAL
9.8 Feb 22

Misskey is an open source, decentralized social media platform. Rated critical severity (CVSS 9.8), this vulnerability i

CVE-2023-52139 CRITICAL
9.6 Dec 29

Misskey is an open source, decentralized social media platform. Rated critical severity (CVSS 9.6), this vulnerability i

CVE-2025-46559 MEDIUM POC
5.4 May 05

Misskey is an open source, federated social media platform. Rated medium severity (CVSS 5.4), this vulnerability is remo

CVE-2026-46713 CRITICAL
9.2 Aug 03

Signature validation bypass in Misskey (versions 12.37.0 through prior to 2026.5.4) allows an attacker to have spoofed A

CVE-2026-47746 HIGH
8.9 Aug 03

JSON-LD signature validation in Misskey's ActivityPub federation layer accepts fraudulent federated activities due to a

CVE-2024-52591 HIGH
8.8 Dec 18

Misskey is an open source, federated social media platform. Rated high severity (CVSS 8.8), this vulnerability is remote

CVE-2024-52590 HIGH
8.8 Dec 18

Misskey is an open source, federated social media platform. Rated high severity (CVSS 8.8), this vulnerability is remote

CVE-2024-25636 HIGH
8.8 Feb 19

Misskey is an open source, decentralized social media platform with ActivityPub support. Rated high severity (CVSS 8.8),

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy