CVE-2025-24897: Misskey Bull Dashboard CSRF Vulnerability

CVE-2025-24897 Overview

CVE-2025-24897 affects Misskey, an open source federated social media platform. The vulnerability stems from missing Cross-Site Request Forgery (CSRF) protection [CWE-352] and insufficient security attributes on the authentication cookies used by the embedded Bull dashboard. Attackers can abuse the bull-board APIs to perform state-changing operations across origins, including adding arbitrary jobs to the queue. The flaw impacts Misskey versions 12.109.0 through releases prior to 2025.2.0-alpha.0.

Critical Impact
Successful exploitation allows attackers to submit arbitrary background jobs to the Bull queue, affecting integrity and availability of the Misskey instance.

Affected Products

Misskey versions 12.109.0 and later
Misskey versions prior to 2025.2.0-alpha.0
Self-hosted Misskey instances exposing the /queue Bull dashboard

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 how Misskey integrates the bull-board administrative dashboard at the /queue path. The dashboard performs authentication using a token cookie issued by the main Misskey frontend. Before the fix, this cookie was set with overly broad scope and lacked the SameSite=Strict and Secure attributes. The bull-board API endpoints also did not validate any anti-CSRF token on state-changing requests.

An attacker can craft a malicious page that, when visited by an authenticated Misskey administrator, issues cross-origin requests to the Bull dashboard APIs. Because the browser automatically attaches the authentication cookie, the requests execute with administrative privileges. The most damaging primitive is the ability to add arbitrary jobs to the queue, which can disrupt instance availability and corrupt processed data.

Root Cause

The root cause is twofold: missing CSRF token validation on the bull-board API surface and authentication cookies without SameSite=Strict and Secure flags. These deficiencies map to [CWE-352] (Cross-Site Request Forgery). User interaction is required because the victim must visit attacker-controlled content while authenticated.

Attack Vector

The attack vector is network-based and requires the victim to render attacker-controlled web content. No prior authentication of the attacker is needed because the victim's session is leveraged through the browser. The scope changes because the vulnerable Bull dashboard sits in a different security context than the main Misskey API.

typescript

// Patch from 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: Misskey commit 77e4210. The patch scopes the authentication cookie to /queue and adds SameSite=Strict and Secure attributes, blocking cross-site cookie attachment to the Bull dashboard.

Detection Methods for CVE-2025-24897

Indicators of Compromise

Unexpected jobs appearing in the Bull queue (/queue dashboard) without a corresponding administrator action.
HTTP requests to /queue/api/* endpoints with Origin or Referer headers pointing to external domains.
Authentication token cookies on the instance lacking SameSite or Secure attributes when inspected in browser developer tools.

Detection Strategies

Review web server access logs for POST or PUT requests under /queue originating from third-party referrers.
Audit the Bull queue history for jobs with abnormal payloads, schedule patterns, or unknown job names.
Compare the running Misskey version against 2025.2.0-alpha.0 to confirm exposure.

Monitoring Recommendations

Enable web application firewall (WAF) logging on the /queue path and alert on cross-origin requests.
Track administrator session cookies for proper SameSite and Secure enforcement after upgrade.
Forward Misskey application and reverse-proxy logs to a centralized SIEM for correlation of queue-related anomalies.

How to Mitigate CVE-2025-24897

Immediate Actions Required

Upgrade Misskey to version 2025.2.0-alpha.0 or later, which scopes the authentication cookie and applies SameSite=Strict and Secure attributes.
Restrict access to the /queue Bull dashboard to trusted administrative networks only.
Invalidate existing administrator sessions after upgrading so new cookies are reissued with the corrected attributes.

Patch Information

The fix is delivered in commit 77e4210 and is included starting with Misskey 2025.2.0-alpha.0. Refer to the GitHub Security Advisory GHSA-38w6-vx8g-67pp and the upstream patch commit for technical details.

Workarounds

Block all access to the /queue directory at the WAF or reverse proxy layer until the patched release can be deployed.
Require administrator IP allow-listing or VPN access for any path under /queue.
Strip or reject cross-origin requests carrying authentication cookies destined for /queue endpoints.

bash

# Example nginx configuration to block external access to the Bull dashboard
location /queue {
    allow 10.0.0.0/8;      # internal admin network
    deny all;
    proxy_pass http://misskey_upstream;
}