Advisory

GHSA-wwrj-3hvj-prpm

Also known as: CVE-2025-66482

Summary

Misskey has a login rate limit bypass via spoofed X-Forwarded-For header

Details

Summary
When using an untrusted reverse proxy or not using a reverse proxy at all, attackers can bypass IP rate limiting by adding a forged X-Forwarded-For header. Starting with version 2025.9.1, an option (trustProxy) has been added in config file to prevent this from happening. However, it is initialized with an insecure default value before version 2025.12.0, making it still vulnerable if the configuration is not set correctly.

Workaround

If you are running Misskey with a trusted reverse proxy, you should *not* be affected by this vulnerability.

  • There is no workaround for the Misskey itself. Please update Misskey to the latest version or set up a trusted reverse proxy.
  • From v2025.9.1 to v2025.11.1, workaround is available. Set trustProxy: false in config file.
  • This is patched in v2025.12.0 by flipping default value of trustProxy to false. If you are using trusted reverse proxy and not remember you manually overrided this value, please take time to check your config for optimal behavior.

Details
Fastify recommend not trusting X-Forwarded-For IPs
Due to misconfiguration in https://github.com/misskey-dev/misskey/blob/develop/packages/backend/src/server/api/SigninApiService.ts#L94 attacks can spoof their IPs.

PoC

POST /api/signin-flow HTTP/1.1
Host: misskey.localhost:3123
Content-Length: 45
Content-Type: application/json
Connection: keep-alive
X-Forwarded-For: 127.1.1.31, 1.1.1.12

{"username":"admin",
	"password":"password"}

image

Impact
An attacker can brute force accounts bypassing rate limiting protection.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-12-15 20:59 UTC
Modified
2026-02-03 03:16 UTC

Affected packages and fixes

misskey-js

npm · All systems

Affected

  • introduced 2025.9.1, fixed 2025.12.0-alpha.2 (semver)

Fixed versions

2025.12.0-alpha.2

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences