Misskey is a popular, open source federated social media platform. Many small and large communities use Misskey for Twitter-like microblogging—self-hosted, customizable, and with a focus on privacy.
But if you’re running Misskey (version >= 12.109. and < 2025.2.-alpha.), you need to know about a serious vulnerability: CVE-2025-24897.

Below, I’ll dive into this vulnerability, show you a simple exploitation scenario, link to references, and tell you how to stay safe.

What Is CVE-2025-24897?

CVE-2025-24897 is a Cross-Site Request Forgery (CSRF) vulnerability affecting the bull-board dashboard, which helps manage the Bull queue system Misskey uses.

Bull-board’s dashboard lacks CSRF protection for some API endpoints.

- Authentication cookies set by the server don’t have secure attributes, making them easier for malicious scripts/sites to use.
- If an admin is logged in and visits a malicious site, that site can send POST requests to /queue (Bull’s admin APIs) as if it were the admin themself.

This means an attacker could, for example, queue up malicious jobs or flood the queue. This risks the stability, reliability, and even integrity of your Misskey instance.

A Walkthrough: How an Attack Might Work

Let’s say a Misskey admin visits a website controlled by an attacker. Maybe it’s a phishing email—or just a booby-trapped ad. If that admin is logged in (or has a valid session cookie), the site secretly submits a request.

With no CSRF checks, this POST request gets *processed* as if the admin really did it.

Imagine the attacker’s website contains

<html>
  <body>
    <form id="csrfForm" action="https://misskey.example.com/queue/api/add-job"; method="POST">
      <input type="hidden" name="data" value='{"job": "dangerousTask", "payload": "do something harmful"}'>
    </form>
    <script>
      document.getElementById('csrfForm').submit();
    </script>
  </body>
</html>

Affected Versions: >=12.109. and <2025.2.-alpha.

- Component: /queue endpoints served by bull-board inside Misskey

The fix commit can be seen here (for illustration, not a real hash).

Permanent Solution

Update Misskey to at least 2025.2.-alpha..

If you can’t upgrade

Block access to the entire /queue directory with your Web Application Firewall (WAF) or reverse proxy:

Example for Nginx

location ^~ /queue/ {
  deny all;
}

Example for Apache

<Directory "/path/to/misskey/public/queue">
    Require all denied
</Directory>

Further Reading & References

- GitHub Security Advisory for CVE-2025-24897
- Misskey Releases
- Bull Board Dashboard

Conclusion

If you're running Misskey and exposing the Bull-board dashboard, this bug (CVE-2025-24897) is a major risk. Update your instance, block /queue for now, and audit your admin interface exposure.

The open source federated social web is only as safe as its least-secured instance. Stay updated—your community’s safety depends on it.


*Exclusive: This guide was written specifically for easy understanding of CVE-2025-24897 with actionable examples. Please always refer to your instance documentation and security team for site-specific advice.*

Timeline

Published on: 02/11/2025 16:15:51 UTC