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

Advisory record · `GHSA-wwrj-3hvj-prpm`

- **Identifiers:** `GHSA-wwrj-3hvj-prpm` · `CVE-2025-66482`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-307](https://cwe.mitre.org/data/definitions/307.html) · [CWE-1188](https://cwe.mitre.org/data/definitions/1188.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [CWE-1188](https://agentprime.io/advisories/tag/cwe-1188.md)
- **Published:** 15 Dec 2025
- **Updated:** 3 Feb 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 15 Dec 2025, 20:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `misskey-js` (npm): affected `>=2025.9.1, <2025.12.0-alpha.2`; fixed in `2025.12.0-alpha.2`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.9 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0034, the 27th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 15 Dec 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-wwrj-3hvj-prpm](https://github.com/advisories/GHSA-wwrj-3hvj-prpm)
- [OSV: GHSA-wwrj-3hvj-prpm](https://osv.dev/vulnerability/GHSA-wwrj-3hvj-prpm)
- <https://github.com/misskey-dev/misskey/security/advisories/GHSA-wwrj-3hvj-prpm>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-66482>
- <https://github.com/misskey-dev/misskey/commit/5512898463fa8487b9e6488912f35102b91f25f7>
- <https://github.com/misskey-dev/misskey>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-wwrj-3hvj-prpm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wwrj-3hvj-prpm/>. Everything for agents: <https://agentprime.io/llms.txt>.