# CVE-2025-24897: Misskey CSRF vulnerability due to insecure configuration of authentication cookie attributes

> Attackers can perform CSRF attacks on Bull dashboard APIs to add arbitrary jobs, impacting availability and integrity.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-38w6-vx8g-67pp

## What is CVE-2025-24897?

CVE-2025-24897 is a high-severity vulnerability in misskey-dev misskey, published on 11 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Misskey is an open source, federated social media platform. Starting in version 12.109.0 and prior to version 2025.2.0-alpha.0, due to a lack of CSRF protection and the lack of proper security attributes in the authentication cookies of Bull's dashboard, some of the APIs of bull-board may be subject to CSRF attacks. There is a risk of this vulnerability being used for attacks with relatively large impact on availability and integrity, such as the ability to add arbitrary jobs. This vulnerability was fixed in 2025.2.0-alpha.0. As a workaround, block all access to the `/queue` directory with a web application firewall (WAF).

Weakness: CWE-614 (Sensitive Cookie in HTTPS Session Without 'Secure' Attribute), CWE-352 (Cross-Site Request Forgery), CWE-1275 (Sensitive Cookie with Improper SameSite Attribute)

## Which versions are affected by CVE-2025-24897?

It affects 1 product.


Products: Misskey Misskey.

## How do I fix CVE-2025-24897?

No fix has been published for CVE-2025-24897 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-24897 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24897 exists.

## Other vulnerabilities in misskey-dev misskey

- [CVE-2025-25306](https://insights.sbomify.com/CVE-2025-25306/): Misskey's Incomplete Patch of CVE-2024-52591 Leads to Forgery of Federated Notes (critical 9.3)
- [CVE-2023-49079](https://insights.sbomify.com/CVE-2023-49079/): Misskey's missing signature validation allows arbitrary users to impersonate any remote user. (critical 9.3)
- [CVE-2026-28431](https://insights.sbomify.com/CVE-2026-28431/): Misskey lacks proper authorization checks and input validation (critical 9.2)
- [CVE-2023-52139](https://insights.sbomify.com/CVE-2023-52139/): Misskey vulnerable to improper authorization when accessing with third-party application (critical 9.1)
- [CVE-2024-52590](https://insights.sbomify.com/CVE-2024-52590/): Missing validation allows spoofed profiles in Misskey (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24897 and fix it if it is affected.

What it is: CVE-2025-24897 is a high-severity vulnerability in misskey-dev misskey, published on 11 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24897 exists.

Affected product: misskey-dev misskey. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-24897/ (Markdown: https://insights.sbomify.com/CVE-2025-24897/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24897
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24897
- OSV: https://osv.dev/vulnerability/CVE-2025-24897

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24897/
Summaries are generated and may contain mistakes; the official description above is the record.