CVE-2025-66402 — misskey.js's export data contains private post data
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+3
- Technical severity (medium)+3
- CISA SSVC: exploitation "poc"+5
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — github.com (NIST National Vulnerability Database)
- Npm Misskey-js: fixed in version 2025.12.0 — github.com (GitHub Security Advisories)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Misskey Misskey, Misskey-dev Misskey, Npm Misskey-js).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Misskey | Misskey |
version 13.0.0-rc11version 13.0.0-beta37version 13.0.0-beta38version 13.0.0-beta39version 13.0.0-beta40version 13.0.0-beta41version 13.0.0-beta42version 13.0.0-beta43 and 29 moreversion 13.0.0-rc1version 13.0.0-rc10version 13.0.0version 13.0.0-rc2version 13.0.0-rc3version 13.0.0-rc4version 13.0.0-rc5version 13.0.0-rc6version 13.0.0-rc7version 13.0.0-rc8version 13.0.0-rc9version 13.0.0-beta35≥ 13.1.0 and < 2025.12.0version 13.0.0-beta16version 13.0.0-beta21version 13.0.0-beta22version 13.0.0-beta23version 13.0.0-beta24version 13.0.0-beta25version 13.0.0-beta26version 13.0.0-beta27version 13.0.0-beta28version 13.0.0-beta29version 13.0.0-beta30version 13.0.0-beta31version 13.0.0-beta32version 13.0.0-beta33version 13.0.0-beta34version 13.0.0-beta36 |
Vulnerable | NIST National Vulnerability Database |
| Misskey-dev | Misskey | version >= 13.0.0-beta.16, < 2025.12.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Npm | Misskey-js | ≥ 13.0.0-beta.16 and < 2025.12.0 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.1 | CVSS 4.0 | High | — | — | security-advisories@github.com via NIST National Vulnerability Database |
| 7.1 | CVSS 4.0 | High | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
| 6.5 | CVSS 3.1 | Medium | 2.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 6.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.31%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · npm/misskey-js
- Affected products added · misskey-dev/misskey
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 6.5
- Source status changed · → Analyzed
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
4 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-104817 Misskey: Lack of rate limiting and size restrictions in RSS fetching API 2d
- High CVE-2026-104816 Misskey: Cross-site scripting in RSS feed item links 2d
- High CVE-2026-103937 Misskey: Denial of service resulting from insufficient cleanup processing during file uploads 2d
- Medium CVE-2026-48115 Misskey: Improper Authorization in the Announcements API Aug 3, 2026
- Critical CVE-2026-46713 Misskey: JSON-LD signature validation + compaction may lead to improper activity handling Aug 3, 2026
- High CVE-2026-47746 Misskey: JSON-LD signature validation + compaction is vulnerable to timing attacks Aug 3, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-66402 is "misskey.js's export data contains private post data", rated Medium. It affects Misskey (Misskey); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.31% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.