CVE-2025-24897: Misskey CSRF Vulnerability

CVE-2025-24897 Overview

CVE-2025-24897 is a Cross-Site Request Forgery (CSRF) vulnerability affecting Misskey, an open source federated social media platform. The flaw exists in versions 12.109.0 through versions prior to 2025.2.0-alpha.0. The vulnerability stems from missing CSRF protection and improper security attributes on the authentication cookies used by the Bull dashboard component. Attackers can abuse exposed bull-board APIs to perform unauthorized actions, including adding arbitrary jobs to the queue. The issue is classified under [CWE-352] and impacts both integrity and availability of affected Misskey instances.

Critical Impact

Attackers can submit arbitrary jobs to the Bull queue through CSRF requests, compromising integrity and availability of Misskey instances.

Affected Products

• Misskey versions 12.109.0 through 2025.1.x
• Misskey Bull dashboard (/queue endpoint)
• Misskey instances prior to 2025.2.0-alpha.0

Discovery Timeline

• 2025-02-11 - CVE-2025-24897 published to the National Vulnerability Database
• 2025-11-26 - Last updated in NVD database

Technical Details for CVE-2025-24897

Vulnerability Analysis

The vulnerability resides in Misskey's integration with bull-board, a dashboard interface for managing Bull job queues. The Bull dashboard authentication cookies lack proper security attributes such as SameSite and Secure. The dashboard endpoints also lack CSRF token validation. An attacker can craft a malicious web page that triggers authenticated requests to a victim's Misskey /queue endpoint when the victim visits the attacker-controlled site.

Successful exploitation requires user interaction, since the victim must visit an attacker-controlled page while authenticated to the Misskey instance. The attacker does not need credentials of their own. Once triggered, the CSRF request can invoke privileged bull-board APIs, including job creation operations.

Root Cause

The root cause is twofold. First, the bull-board routes mounted under /queue do not enforce anti-CSRF tokens on state-changing requests. Second, the authentication cookie issued for the dashboard was scoped to the entire site without SameSite=Strict or Secure flags, allowing cross-origin requests to carry the cookie.

Attack Vector

The attack vector is network-based and requires user interaction. An attacker hosts a webpage containing forged form submissions or fetch requests targeting /queue API routes on the victim's Misskey instance. When an authenticated administrator visits the page, the browser automatically includes the dashboard authentication cookie. The forged request is processed as if it originated from the legitimate user.

// Security patch in packages/frontend/src/account.ts
function fetchAccount(token: string, id?: string, forceShowDialog?: boolean): Promise<Account> {
	document.cookie = "token=; path=/; max-age=0";
	document.cookie = `token=${token}; path=/queue; max-age=86400; SameSite=Strict; Secure`; // bull dashboardの認証とかで使う

	return new Promise((done, fail) => {
		window.fetch(`${apiUrl}/i`, {
			method: 'POST',

Source: GitHub Commit 77e4210

The patch scopes the token cookie to the /queue path and adds SameSite=Strict and Secure attributes. This prevents the cookie from being sent on cross-site requests, blocking the CSRF attack chain.

Detection Methods for CVE-2025-24897

Indicators of Compromise

• Unexpected jobs appearing in the Bull queue without corresponding administrator activity
• HTTP requests to /queue endpoints with Origin or Referer headers pointing to external domains
• Authentication cookies for the Bull dashboard being transmitted on cross-site requests
• Anomalous spikes in queue job creation outside normal operational windows

Detection Strategies

• Inspect web server access logs for POST requests to /queue/* paths originating from unfamiliar Referer headers
• Compare administrator session activity against queue modification events for correlation gaps
• Audit Bull dashboard activity logs for job submissions that do not match legitimate administrative workflows

Monitoring Recommendations

• Enable verbose logging on the reverse proxy in front of Misskey for all /queue requests
• Forward web access logs to a centralized SIEM and alert on cross-origin Referer patterns
• Monitor the Bull queue for unexpected job types or unusually high creation rates

How to Mitigate CVE-2025-24897

Immediate Actions Required

• Upgrade Misskey to version 2025.2.0-alpha.0 or later, which contains the patched cookie attributes
• Restrict access to the /queue directory at the network or reverse-proxy layer until the upgrade is complete
• Force re-authentication of administrators after upgrading to invalidate cookies issued without secure attributes

Patch Information

The vulnerability is fixed in Misskey version 2025.2.0-alpha.0 via commit 77e4210. The patch sets the authentication cookie path to /queue and adds SameSite=Strict and Secure flags. Review the GitHub Security Advisory GHSA-38w6-vx8g-67pp and the upstream commit for complete details.

Workarounds

• Block all external access to the /queue directory using a web application firewall (WAF) rule
• Restrict the Bull dashboard to internal IP ranges or VPN-only access via reverse-proxy ACLs
• Require administrators to access the Bull dashboard through a dedicated browser profile to limit cookie exposure

# Example nginx configuration to block external access to /queue
location /queue {
    allow 10.0.0.0/8;
    allow 192.168.0.0/16;
    deny all;
    proxy_pass http://misskey_backend;
}