dbcve.org
MisskeyApplication

CVE-2024-52591

CRITICAL · 9.3 CVSS v3.1 Published 2024-12-18
Fix available
A fix is available. Upgrade to 2024.11.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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` and `HttpRequestService.getActivityJson` allows an attacker to create fake user profiles and forged notes. The spoofed users will appear to be from a different instance than the one where they actually exist, and the forged notes will appear to be posted by a different user. Vulnerable Misskey instances will accept the spoofed objects as valid, allowing an attacker to impersonate other users and instances. The attacker retains full control of the spoofed user / note and can 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 versions before 2024.11.0-alpha.3 lack proper validation in the ActivityPub request handling functions (ApRequestService.signedGet and HttpRequestService.getActivityJson), allowing attackers to craft spoofed user profiles and forged notes with falsified origin information. This enables complete impersonation of users and instances on the federated network by bypassing signature verification.

MitigationUpgrade Misskey to version 2024.11.0-alpha.3 or later. No workarounds exist; immediate patching is required given the critical CVSS score and complete account impersonation capability.

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.11.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
Changed
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/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. Determine installed Misskey version
    Run 'grep -r "version" /opt/misskey/package.json' or check the package.json file in the Misskey installation directory. You can also check via the admin dashboard under 'About' section if available.
    Affected if The version is below 2024.11.0 or exactly equals 2024.11.0 (versions 2024.11.0-alpha.3 and later are fixed).
  2. Confirm federation is enabled
    Check the Misskey configuration file (default.yml or .env) for the 'federation' or 'enablePublicTimeline' settings. In the admin dashboard, verify that 'Federation' is not disabled under the settings.
    Affected if Federation and ActivityPub handling are enabled (this is default behavior for most Misskey instances). Since the vulnerability lies in ActivityPub request handling, any instance with federation active can be exploited.

You are affected if your Misskey installation version is below 2024.11.0 (or exactly 2024.11.0) AND federation/ActivityPub is enabled on your instance.

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; immediate patching is required given the critical CVSS score and complete account impersonation capability.

Recommended fix High confidence

2024.11.0 or later stable release (2024.11.0-alpha.3 contains the fix, but upgrade to latest stable 2024.11.x release)

  1. 1. Back up your Misskey instance database and configuration files before upgrading
  2. 2. Stop the Misskey service
  3. 3. If using Docker, pull the latest image: docker pull misskey/misskey:latest
  4. 4. If using a manual installation, navigate to your Misskey directory and run: git fetch && git checkout 2024.11.0
  5. 5. Install dependencies: npm install
  6. 6. Build the project: NODE_ENV=production npm run build
  7. 7. Restart the Misskey service
  8. 8. Verify the version by checking the admin panel or running: cat ../../../misskey/built/static/ver.json
Caveat Review release notes for 2024.11.0 for any breaking changes to plugins or API compatibility before upgrading

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

Fix this in Misskey Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52591 — 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-52591 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