{"answers":{"affected":"2 open source packages ship an affected version, including misskey-js. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66482 exists.","fix":"Upgrade misskey-js to 2025.12.0-alpha.2 or later.","what":"CVE-2025-66482 is a medium-severity vulnerability in misskey-dev misskey, published on 15 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-66482 and fix it if it is affected.\n\nWhat it is: CVE-2025-66482 is a medium-severity vulnerability in misskey-dev misskey, published on 15 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66482 exists.\n\nAffected packages and fixed versions:\n- misskey-js (npm): affected from 2025.9.1; fixed in 2025.12.0-alpha.2\n- misskey-js (npm): affected from 2025.9.1; fixed in 2025.12.0-alpha.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-66482/ (Markdown: https://insights.sbomify.com/CVE-2025-66482/index.md)","id":"CVE-2025-66482","markdown":"https://insights.sbomify.com/CVE-2025-66482/index.md","name":"CVE-2025-66482","record":{"aliases":["GHSA-wwrj-3hvj-prpm"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Misskey social platform","requires_auth":"none","summary":"Attackers can bypass IP rate limiting by spoofing the X-Forwarded-For header when using an untrusted reverse proxy or no proxy.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"misskey","vendor":"misskey"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"},{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"Misskey is an open source, federated social media platform. Attackers who use an untrusted reverse proxy or not using a reverse proxy at all 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-alpha.2, making it still vulnerable if the configuration is not set correctly. This is patched in v2025.12.0-alpha.2 by flipping default value of `trustProxy` to `false`. Users of a trusted reverse proxy who are unsure if they manually overode this value should check their config for optimal behavior. Users are running Misskey with a trusted reverse proxy should not be affected by this vulnerability. From v2025.9.1 to v2025.11.1, workaround is available. Set `trustProxy: false` in config file.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Misskey has a login rate limit bypass via spoofed X-Forwarded-For header","id":"CVE-2025-66482","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Multiple vulnerabilities have been addressed in IBM Aspera Shares","id":"CVE-2025-66483"},"packages":[{"ecosystem":"npm","fixed":["2025.12.0-alpha.2"],"introduced":["2025.9.1"],"last_affected":[],"package":"misskey-js","purl":null,"source":"GHSA-wwrj-3hvj-prpm"},{"ecosystem":"npm","fixed":["2025.12.0-alpha.2"],"introduced":["2025.9.1"],"last_affected":[],"package":"misskey-js","purl":"pkg:npm/misskey-js","source":"GHSA-wwrj-3hvj-prpm"}],"prev":{"headline":"DeepChat's Incomplete XSS Fix Allows RCE through Mermaid Content","id":"CVE-2025-66481"},"products":["misskey"],"published":"2025-12-15","related":[{"cvss_score":9.3,"headline":"Misskey's Incomplete Patch of CVE-2024-52591 Leads to Forgery of Federated Notes","id":"CVE-2025-25306","kev_date_added":null,"published":"2025-03-10"},{"cvss_score":9.3,"headline":"Misskey's missing signature validation allows arbitrary users to impersonate any remote user.","id":"CVE-2023-49079","kev_date_added":null,"published":"2023-11-29"},{"cvss_score":9.2,"headline":"Misskey lacks proper authorization checks and input validation","id":"CVE-2026-28431","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":9.1,"headline":"Misskey vulnerable to improper authorization when accessing with third-party application","id":"CVE-2023-52139","kev_date_added":null,"published":"2023-12-29"},{"cvss_score":8.8,"headline":"Missing validation allows spoofed profiles in Misskey","id":"CVE-2024-52590","kev_date_added":null,"published":"2024-12-18"},{"cvss_score":8.8,"headline":"Missing validation allows spoofed profiles and notes in Misskey","id":"CVE-2024-52591","kev_date_added":null,"published":"2024-12-18"},{"cvss_score":8.8,"headline":"SQL injection of notes/search-by-tag","id":"CVE-2023-24812","kev_date_added":null,"published":"2023-02-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-16","vendors":["misskey-dev"]},"summary":"Attackers can bypass IP rate limiting by spoofing the X-Forwarded-For header when using an untrusted reverse proxy or no proxy.","url":"https://insights.sbomify.com/CVE-2025-66482/"}