Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker operates or controls a federating server
-
DeliveryCraft JSON-LD activity exploiting compaction/signature mismatch
-
ExploitDeliver forged activity to victim instance
-
ExecutionSignature validation incorrectly accepts spoofed activity
-
ImpactForged activity attributed to trusted actor (impersonation/integrity compromise)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
|
| Exploitation Conditions | Exploitation requires the target Misskey instance (version 12.37.0 up to 2026.5.4) to process federated ActivityPub activities that use JSON-LD/Linked Data signatures - i.e., the server must be participating in federation and accept and validate signed activities from remote actors, which is the default and intended operating mode for a fediverse server. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), no authentication or user interaction is needed and attack complexity is low. The main limiting factor is federation reachability: the attacker must be able to deliver activities to the victim instance, so instances that block, allow-list, or disable federation with the attacker's server are not exposed via that path. No specific non-default configuration toggle is called out in the available data beyond running an affected version with federation enabled. |
| Impact | The signals are largely consistent toward high priority: the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) indicates remote, unauthenticated, low-complexity exploitation with no user interaction, and the impact metrics stress integrity (VI:H, SI:H) with limited confidentiality (VC:L) and no availability impact, yielding a 9.2 Critical rating. This aligns with a signature-spoofing bug whose primary danger is forged/authoritative-looking activities rather than data destruction. Mitigating the raw severity: exploitation requires participation in the federated network (the target instance must accept federation from the attacker), and no EPSS score, POC, or KEV entry is provided, so there is no evidence of active or automated mass exploitation at this time. The 'Information Disclosure' tag partly conflicts with the vector's integrity-dominant profile - the realistic worst case is impersonation/spoofing of activities rather than bulk data leakage. Net: treat as a real, high-priority patch for any internet-facing federated Misskey instance, but current evidence points to potential targeted abuse rather than confirmed widespread exploitation. |
| Exploit ScenarioDerived | A malicious or attacker-controlled fediverse server crafts a JSON-LD ActivityPub activity that exploits the compaction/signature mismatch so that forged content appears to be validly signed by a trusted actor. The victim Misskey instance accepts and processes the spoofed activity (e.g., attributing a post or action to another user or instance), enabling impersonation and integrity manipulation across the federated network. No public exploit has been identified at time of analysis, and the network, low-complexity, unauthenticated vector means exploitation requires only that the target federates with the attacker. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 03, 2026
Signature validation bypass in Misskey (versions 12.37.0 through prior to 2026.5.4) allows an attacker to have spoofed ActivityPub activities accepted as authentic. The flaw resides in the JSON-LD signature validation and compaction logic (CWE-347), enabling forgery of federated actions such as posts or actions attributed to other actors/instances. The CVSS 4.0 base score is 9.2 (Critical) with a network, unauthenticated, low-complexity vector emphasizing integrity impact; no public exploit has been identified at time of analysis, and it is not listed in CISA KEV.
RemediationAI
Vendor-released patch: upgrade to Misskey 2026.5.4, which bundles fixes for this issue (GHSA-w8x2-gpq6-jxvf / CVE-2026-46713) alongside four other advisories addressed in the same release. Follow the upgrade instructions in the release notes at https://github.com/misskey-dev/misskey/releases/tag/2026.5.4 and review the advisory at https://github.com/misskey-dev/misskey/security/advisories/GHSA-w8x2-gpq6-jxvf. If immediate upgrade is not possible, meaningful compensating controls are limited because the flaw is in core federation processing; operators can reduce exposure by restricting or pausing federation with untrusted or unknown remote instances (using Misskey's instance blocking/allow-list or moving to a more restrictive federation policy), accepting the trade-off that this breaks legitimate interaction with those servers, and by monitoring for anomalous or impersonated activities from remote actors. These are stopgaps only - patching to 2026.5.4 is the reliable fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Misskey is an open-source, federated (fediverse) social media server that speaks the ActivityPub protocol. In ActivityPub federation, remote servers authenticate the origin and integrity of incoming activities using cryptographic signatures, and JSON-LD documents are 'compacted'/normalized before the signature is verified. This CVE is a CWE-347 (Improper Verification of Cryptographic Signature) weakness in that JSON-LD signature validation and compaction pipeline: discrepancies between what is signed and what is processed after compaction allow a forged document to pass verification. The affected component is identified by CPE cpe:2.3:a:misskey-dev:misskey covering all versions in the vulnerable range. The 'Jwt Attack' tag is likely a loose categorization of the signature-forgery class rather than literal JWT usage, since ActivityPub relies on Linked Data / HTTP signatures rather than JWTs.
Know when Misskey gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:H/SA:N
Remote unauthenticated signature bypass with no user interaction gives AV:N/AC:L/PR:N/UI:N; forged activities affect other federated actors/instances so S:C with I:H, limited C:L, and no availability impact.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
Misskey is an open source, federated social media platform. Versions 12.37.0 and later, but prior to 2026.5.4, contain a vulnerability in the JSON-LD signature validation and compaction process that allows spoofed activities to be accepted as valid. This issue has been fixed in version 2026.5.4.
Executive ViewAI
A critical signature validation flaw in Misskey versions 12.37.0 through 2026.5.3 allows unauthenticated attackers to forge authenticated ActivityPub activities, enabling impersonation of users and instances across federated networks. Any organization deploying affected Misskey versions faces immediate exposure to spoofed communications, account takeover-equivalent attacks, and coordinated disinformation campaigns.
No vendor-released patch identified at time of analysis. No public exploit identified at time of analysis. Interim mitigations: (1) disable ActivityPub federation to untrusted instances; (2) implement external cryptographic verification of signatures at the application layer; (3) restrict federation to explicitly pre-authorized trusted peers only; (4) deploy monitoring for anomalous actor and object relationships in ActivityPub activities.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Misskey is an open source, decentralized microblogging platform. Rated high severity (CVSS 7.5), this vulnerability is r
Missing authorization checks in Misskey's favorites and clips export feature allow any authenticated user to read the co
Login rate-limit bypass in Misskey (versions 2025.9.1 through 2025.11.x, and up to but not including 2025.12.0-alpha.2)
Misskey before 10.102.4 allows hijacking a user's token. Rated medium severity (CVSS 6.1), this vulnerability is remotel
Misskey is an open source, decentralized social media platform. Rated critical severity (CVSS 9.8), this vulnerability i
Misskey is an open source, decentralized social media platform. Rated critical severity (CVSS 9.6), this vulnerability i
Misskey is an open source, federated social media platform. Rated medium severity (CVSS 5.4), this vulnerability is remo
JSON-LD signature validation in Misskey's ActivityPub federation layer accepts fraudulent federated activities due to a
Misskey is an open source, federated social media platform. Rated high severity (CVSS 8.8), this vulnerability is remote
Misskey is an open source, federated social media platform. Rated high severity (CVSS 8.8), this vulnerability is remote
Misskey is an open source, decentralized social media platform with ActivityPub support. Rated high severity (CVSS 8.8),
Client-side DOM cross-site scripting in Misskey's RSS widgets lets an attacker who controls or can inject into a feed th
EUVD-2026-52485
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB