misskey-js
Affected
- introduced
2025.9.1, fixed2025.12.0-alpha.2(semver)
Fixed versions
2025.12.0-alpha.2
Fix
- Fixed version
2025.12.0-alpha.2npm install [email protected]
Advisory
Also known as: CVE-2025-66482
Misskey has a login rate limit bypass via spoofed X-Forwarded-For header
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.
trustProxy: false in config file.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"}
Impact
An attacker can brute force accounts bypassing rate limiting protection.
Medium Basis: The source's own band: MODERATE
2025.9.1, fixed 2025.12.0-alpha.2 (semver)2025.12.0-alpha.2
2025.12.0-alpha.2npm install [email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0