Skip to main content
VulnerabilityPublished Updated

CVE-2026-46714: misskey · Uncontrolled Recursion

Affects misskeySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 2026.5.4 when convenient.

Data as of 1 Nov 2026, 22:58 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% 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:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:N/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
misskey-devmisskeyAffected
  • >=8.63.0 <2026.5.4
Fixed in
  • 2026.5.4
GitHubmisskey-dev/misskeypkg:github/misskey-dev/misskeyOther threatsAffected
  • >=8.63.0 <2026.5.4
Fixed in
  • 2026.5.4

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, where this vulnerability has been fixed. No other mitigation steps are indicated.

Description

Misskey is an open source, federated social media platform. IVersions 8.63.0 and later, but prior to 2026.5.4, contain a vulnerability that can cause the Misskey web client to slow down or crash when it applies a malformed theme. This issue has been fixed in version 2026.5.4.

References

Community reviews

Loading reviews…