GHSA-wwrj-3hvj-prpm is a medium-severity (CVSS 6.5) CWE-307 vulnerability in misskey-js. O3 Security confirms whether GHSA-wwrj-3hvj-prpm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Misskey has a login rate limit bypass via spoofed X-Forwarded-For header
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
misskey-jsnpmDescription
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: falsein config file. - This is patched in v2025.12.0 by flipping default value of
trustProxytofalse. 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | misskey-js | ≥ 2025.9.1&&< 2025.12.0-alpha.2 | 2025.12.0-alpha.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for misskey-js. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update misskey-js to 2025.12.0-alpha.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wwrj-3hvj-prpm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-wwrj-3hvj-prpm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-wwrj-3hvj-prpm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-wwrj-3hvj-prpm in your dependencies?
O3 detects GHSA-wwrj-3hvj-prpm across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.