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.
Published: 2026-08-03
Score: 2.3 Low
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Misskey versions 2025.3.2 through the release before 2026.5.4 have a missing permission check that allows an attacker to retrieve certain data points from the Direct Messaging module regardless of the user’s account permissions. The flaw enables the disclosure of private message content and related metadata, breaching confidentiality. The weakness is formally categorized as CWE‑639—Authorization Bypass Through User‑Controlled Key. The vulnerability is not limited to federated instances; it persists whether or not federation is enabled, meaning that any user with access to the application can potentially exploit the flaw.

Affected Systems

The affected product is the open‑source Misskey platform developed by misskey‑dev. All releases from version 2025.3.2 up to, but excluding, 2026.5.4 are impacted. The only unaffected content are notes created with the “specified” (formerly “direct”) visibility setting, which is not susceptible to the unchecked access.

Risk and Exploitability

The vulnerability carries a CVSS score of 2.3, indicating low severity. No EPSS value is reported, leaving the likelihood of exploitation uncertain but presumed low. The issue is not listed in the CISA Known Exploited Vulnerabilities catalog. Although the attack vector is not explicitly detailed, it is inferred that any user able to interact with the Direct Messaging API—whether locally or over the network—could read protected message data. The scope of compromise affects confidentiality for all users on the instance, with no direct impact on integrity or availability.

Generated by OpenCVE AI on August 4, 2026 at 09:39 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to Misskey version 2026.5.4 or later, which implements the required permission checks for the Direct Messaging feature.
  • If an immediate upgrade is not feasible, restrict access to the Direct Messaging API to authenticated and authorized users only; consider disabling the endpoint for unauthenticated or unauthorized requests via firewall or application configuration.
  • Review and enforce role‑based access controls around message reads, ensuring that only intended recipients can view message content, following the guidance for CWE‑639 remediation by verifying user identity before data exposure.

Generated by OpenCVE AI on August 4, 2026 at 09:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 05 Aug 2026 10:00:00 +0000

Type Values Removed Values Added
First Time appeared Misskey
Misskey misskey
Vendors & Products Misskey
Misskey misskey

Tue, 04 Aug 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 03 Aug 2026 21:45:00 +0000

Type Values Removed Values Added
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.
Title Misskey: Lack of proper permission checks in Direct Messaging feature
Weaknesses CWE-639
References
Metrics cvssV4_0

{'score': 2.3, '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'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-04T15:55:04.271Z

Reserved: 2026-05-15T23:26:58.309Z

Link: CVE-2026-46712

cve-icon Vulnrichment

Updated: 2026-08-04T15:54:56.769Z

cve-icon NVD

Status : Received

Published: 2026-08-03T22:16:48.863

Modified: 2026-08-04T17:16:54.290

Link: CVE-2026-46712

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-05T09:45:06Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key