Misskey
CVE-2025-66402
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged account
-
DeliveryObtain private post IDs from victim profile
-
ExploitAdd private posts to favorites or clips
-
ExecutionExport favorites/clips data
-
ImpactRead exfiltrated private post contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated account on the target Misskey instance (PR:L) and the ability to add specific private posts - followers-only or direct notes the attacker cannot normally view - to the attacker's own favorites or clips, which presupposes obtaining those posts' note IDs/URLs (the advisory notes pinned private post IDs can be harvested from the victim's user page). The attacker then triggers the standard favorites/clips export job, which in affected versions skipped visibility enforcement. Limiting factors: a valid local account is mandatory, the attacker must already know or discover the private note identifiers, and only confidentiality of exposed notes is affected - there is no integrity or availability impact and no unauthenticated path. |
| Impact | This is a missing-authorization flaw (CWE-862) where the favorites/clips export feature in Misskey fails to re-apply note visibility checks, letting an authenticated user exfiltrate the contents of followers-only and direct posts they were never permitted to read. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N) scores 7.1 and is internally consistent with the description: network reachable, low attack complexity, low privileges (a valid account), no user interaction, and a pure confidentiality impact with no integrity or availability effect. A working PoC is published in the GHSA advisory and the patch commit is public, so publicly available exploit code exists; however, there is no CISA KEV listing and no EPSS value was supplied, so there is no evidence of active or widespread exploitation - the signals point to a disclosed, easily reproducible but not-yet-weaponized data-exposure bug rather than an urgent mass-exploitation threat. The practical ceiling on impact is that the attacker must first obtain the target's private note IDs (e.g., via pinned private posts shown on the user page) and must have an account on the same instance, which makes this a targeted-disclosure risk rather than a trivial bulk scrape. |
| Exploit ScenarioDerived | An authenticated user on a Misskey instance obtains the IDs/URLs of another user's followers-only or direct posts (for example from pinned private posts visible on the victim's profile), adds those posts to their own favorites or clips, and then uses the built-in export feature; the exported file contains the full private post contents despite the attacker never having view permission. A step-by-step PoC confirming this (verified on v2025.11.1) is published in the GHSA advisory, and the fix adds visibility-query enforcement to the export processors. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Missing authorization checks in Misskey's favorites and clips export feature allow any authenticated user to read the contents of followers-only and direct posts they were never permitted to view, affecting versions from 13.0.0-beta.16 up to (but not including) 2025.12.0. The export jobs (ExportFavorites / ExportClips) serialize notes without reapplying note visibility rules, so an attacker who can add a private note ID or URL to their own favorites or clips - for example by harvesting the ID of a pinned private post from the victim's public user page - can simply export and read the private content. Publicly available exploit code exists (the GitHub Security Advisory GHSA-496g-mmpw-j9x3 includes a full proof-of-concept against v2025.11.1); exploitation requires a valid local account but no special privileges, and the impact is confidentiality-only with no integrity or availability effect. Vendor-released patch: 2025.12.0.
RemediationAI
Upgrade Misskey to 2025.12.0 or later, the vendor-released patch version that reintroduces visibility enforcement inside the export processors (fix commit dc77d59f8712d3fe0b73cd4af2035133839cd57b, advisory https://github.com/misskey-dev/misskey/security/advisories/GHSA-496g-mmpw-j9x3); if you consume the misskey-js npm package, update to 2025.12.0 as well. If immediate upgrade is not possible, apply compensating controls knowing their trade-offs: disable or restrict the data-export capability for untrusted roles through Misskey's role/permission system (this removes a legitimate user feature and may irritate users, but blocks the entire attack path since triggering the export job is mandatory), and temporarily stop or drain the export queue workers so pending export jobs cannot complete (this halts all exports globally). Additionally, review existing export archives for notes the exporting account was not entitled to see, and where privacy is critical, educate users that pinned followers-only or direct posts expose their note IDs on their public profile page - unpinning such posts reduces identifier discovery, though it does not by itself fix the underlying flaw. Note there is no configuration-only fix that preserves export functionality; upgrading is required.
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Misskey is a federated (ActivityPub) social platform written in TypeScript on a NestJS backend with TypeORM repositories. The root cause is CWE-862 (Missing Authorization): the note-packing path in packages/backend/src/core/entities/NoteEntityService.ts correctly gates access to notes via visibility checks (followers-only / direct / hiddenBefore / followersOnlyBefore time windows), but the background export processors - ExportClipsProcessorService.ts and its favorites counterpart - queried ClipNote and Favorites rows directly through TypeORM find() calls with no visibility predicate, so notes the exporting user could not read were still serialized into the export archive. The fix (commit dc77d59f8712d3fe0b73cd4af2035133839cd57b) replaces those repository find() calls with QueryBuilder queries that invoke QueryService.generateVisibilityQuery(query, { id: userId }) and a new extracted helper shouldHideNoteByTime() to re-enforce the same time-based hiding rules (negative values interpreted as elapsed-seconds windows, positive values as absolute UNIX timestamps) that the normal API path applies. Because the vulnerability is purely a missing check rather than a memory-safety or injection bug, the assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, consistent with the supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N).
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
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable export feature abusable by any authenticated account (PR:L, AC:L, UI:N) leaking private post contents only, so C:H with I:N/A:N and unchanged scope.
Primary rating from Vendor (github).
CVSS VectorVendor: github
DescriptionCVE.org
Misskey is an open source, federated social media platform. Starting in version 13.0.0-beta.16 and prior to version 2025.12.0, an actor who does not have permission to view favorites or clips can can export the posts and view the contents. Version 2025.12.0 fixes the issue.
Executive ViewAI
Misskey, a decentralized social media platform, is affected by a high-severity vulnerability that compromises the confidentiality of private user communications. Publicly available exploit code exists, and Vendor-released patch: 2025.12.0. This breach affects all users who trust the platform with private messages, and leadership should act swiftly to patch and protect user data.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Affected Products (CPE)CVE.org
Misskey is an open source, decentralized microblogging platform. Rated high severity (CVSS 7.5), this vulnerability is r
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)
Misskey before 10.102.4 allows hijacking a user's token. Rated medium severity (CVSS 6.1), this vulnerability is remotel
Misskey is an open source, decentralized social media platform. Rated critical severity (CVSS 9.8), this vulnerability i
Misskey is an open source, decentralized social media platform. Rated critical severity (CVSS 9.6), this vulnerability i
Misskey is an open source, federated social media platform. Rated medium severity (CVSS 5.4), this vulnerability is remo
Signature validation bypass in Misskey (versions 12.37.0 through prior to 2026.5.4) allows an attacker to have spoofed A
JSON-LD signature validation in Misskey's ActivityPub federation layer accepts fraudulent federated activities due to a
Misskey is an open source, federated social media platform. Rated high severity (CVSS 8.8), this vulnerability is remote
Misskey is an open source, federated social media platform. Rated high severity (CVSS 8.8), this vulnerability is remote
Misskey is an open source, decentralized social media platform with ActivityPub support. Rated high severity (CVSS 8.8),
Client-side DOM cross-site scripting in Misskey's RSS widgets lets an attacker who controls or can inject into a feed th
NVD
CVE.org
EPSS
GitHub
Exploit-DB