{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46559 exists.","fix":"No fix has been published for CVE-2025-46559 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46559 is a medium-severity path traversal vulnerability in misskey-dev misskey, published on 5 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-46559 and fix it if it is affected.\n\nWhat it is: CVE-2025-46559 is a medium-severity path traversal vulnerability in misskey-dev misskey, published on 5 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46559 exists.\n\nAffected product: misskey-dev misskey. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-46559/ (Markdown: https://insights.sbomify.com/CVE-2025-46559/index.md)","id":"CVE-2025-46559","markdown":"https://insights.sbomify.com/CVE-2025-46559/index.md","name":"CVE-2025-46559","record":{"aliases":["GHSA-gmq6-738q-vjp2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Misskey social platform","requires_auth":"low_privilege","summary":"Attackers can use malicious AiScript to bypass API restrictions and access unauthorized endpoints like files or proxies via path traversal.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"misskey","vendor":"misskey"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Misskey is an open source, federated social media platform. Starting in version 12.31.0 and prior to version 2025.4.1, missing validation in `Mk:api` allows malicious AiScript code to access additional endpoints that it isn't designed to have access to. The missing validation allows malicious AiScript code to prefix a URL with `../` to step out of the `/api` directory, thereby being able to make requests to other endpoints, such as `/files`, `/url`, and `/proxy`. Version 2025.4.1 fixes the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Misskey Directory Traversal Vulnerability in AiScript via `Mk:api`","id":"CVE-2025-46559","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"vLLM phi4mm: Quadratic Time Complexity in Input Token Processing​ leads to denial of service","id":"CVE-2025-46560"},"packages":[],"prev":{"headline":"org.xwiki.contrib.markdown:syntax-markdown-commonmark12 vulnerable to XSS via Markdown content","id":"CVE-2025-46558"},"products":["misskey"],"published":"2025-05-05","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":"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-05","vendors":["misskey-dev"]},"summary":"Attackers can use malicious AiScript to bypass API restrictions and access unauthorized endpoints like files or proxies via path traversal.","url":"https://insights.sbomify.com/CVE-2025-46559/"}