NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2025-66402: misskey.js's export data contains private post data

highCVSS 4.0 7.1 · 3.1 6.5GHSA-496g-mmpw-j9x3

Summary After adding private posts (followers, direct) that you do not have permission to view to your favorites or clips, you can export them to view the contents of the private posts. PoC 1. Create an account (X) for testing and an account (Y) for private posts on the same server. 2. Send appropriate content from Y using "Follow" 3. Send appropriate content to any user using "Nominate" from Y 4.

Published Dec 15, 2025 · Updated Jan 6, 2026

Affected packages

misskey-js

Ecosystem
npm
Affected
>= 13.0.0-beta.16, < 2025.12.0
Fixed in
2025.12.0
Check
npm ls misskey-js

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Summary

After adding private posts (followers, direct) that you do not have permission to view to your favorites or clips, you can export them to view the contents of the private posts.

PoC

  1. Create an account (X) for testing and an account (Y) for private posts on the same server.
  2. Send appropriate content from Y using "Follow"
  3. Send appropriate content to any user using "Nominate" from Y
  4. Obtain the URLs for the two posts above using Y's account.
  5. Query the URLs for the two posts using X and add them to your favorites or clips.
  6. Export your favorites or clips using X.
  7. Check the exported data.

Note: Verified in v2025.11.1

Impact

This could allow an attacker to view the contents of private posts. If you have pinned private posts, this could be a real problem, as the ID of the private post can be obtained by viewing the user page on the original server.

Credited to na2204, samunohito.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries