CVE-2026-46712: misskey · Insecure Direct Object Reference
Affects misskeySource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 2026.5.4 when convenient.
Data as of 1 Nov 2026, 22:58 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.5.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.
What to do
Upgrade misskey and misskey-dev/misskey to 2026.5.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| misskey-devmisskey | Affected
| Fixed in
|
GitHubmisskey-dev/misskeypkg:github/misskey-dev/misskeyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Misskey version 2026.5.4 or later to apply the official fix. There is no indication of temporary workarounds or partial mitigations. Patch status is confirmed by the vendor advisory stating the issue is fixed in 2026.5.4.
Description
Misskey versions from 2025.3.2 up to but not including 2026.5.4 contain an authorization bypass vulnerability in the Direct Messages feature. This flaw allows access to certain data points without proper permission checks, regardless of account permissions or federation settings. Notes with specified (formerly direct) visibility are not affected. The issue is fixed in version 2026.5.4.