dbcve.org
MisskeyApplication

CVE-2024-52590

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-18
Fix available
A fix is available. Upgrade to 2024.11.0 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Misskey is an open source, federated social media platform. In affected versions missing validation in `ApRequestService.signedGet` allows an attacker to create fake user profiles that appear to be from a different instance than the one where they actually exist. These profiles can be used to impersonate existing users from the target instance. Vulnerable Misskey instances will accept spoofed users as valid, allowing an attacker to impersonate users on another instance. Attackers have full control of the spoofed user and can post, renote, or otherwise interact like a real account. This issue has been addressed in version 2024.11.0-alpha.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Misskey's ActivityPub request service (signedGet) lacks proper instance origin validation, allowing attackers to forge federated user profiles that appear to originate from other instances. This enables complete account impersonation in the fediverse, as vulnerable instances accept spoofed users as legitimate.

MitigationUpgrade Misskey to version 2024.11.0-alpha.3 or later. No workarounds exist; this is an authentication validation fix requiring code changes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MisskeyApplication
Affected:> 2024.8.0, < 2024.11.0= 2024.8.0= 2024.11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Misskey version via admin panel
    Log into the Misskey administration interface and locate the version information typically displayed on the dashboard or in System > About. Alternatively, check the package.json file in the Misskey installation directory for the 'version' field.
    Affected if The displayed version is 2024.8.0, 2024.9.0, 2024.10.0, or 2024.11.0 (any version >= 2024.8.0 and <= 2024.11.0).
  2. Verify ActivityPub federation is enabled
    In the Misskey admin panel, navigate to Settings > Federation or the federation configuration section. Confirm that federation functionality is turned on. This is the default setting for most Misskey instances.
    Affected if Federation/ActivityPub is enabled, which is required for the vulnerability to be exploitable.
  3. Confirm instance participates in the fediverse
    Check if the instance has any federated users or posts in the federated timeline. Look for incoming or outgoing activity from other instances, or check the instance info endpoint for linked peers.
    Affected if The instance has federated with other ActivityPub servers, meaning it processes incoming user profiles from other instances.

An instance is affected if it runs Misskey version 2024.8.0 through 2024.11.0 and has ActivityPub federation enabled, as the signedGet function lacks proper origin validation in those versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2024.11.0 or later
Fixed in 2024.11.0
Interim mitigation

Upgrade Misskey to version 2024.11.0-alpha.3 or later. No workarounds exist; this is an authentication validation fix requiring code changes.

Recommended fix High confidence

Misskey 2024.11.0 or later (specifically 2024.11.0-alpha.3及以上)

  1. 1. Backup your Misskey instance database and configuration files before proceeding
  2. 2. Stop the Misskey service
  3. 3. Update to Misskey version 2024.11.0 or later (the official description references 2024.11.0-alpha.3 as the fixed release)
  4. 4. Verify the installation by checking the version number
  5. 5. Restart the Misskey service
  6. 6. Test federated interactions to confirm the fix works correctly
Caveat Review release notes for any breaking changes between your current version and 2024.11.0; alpha versions may have additional stability considerations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Misskey Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,340
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52590 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-52590 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data