# CVE-2025-46559: Misskey Directory Traversal Vulnerability in AiScript via `Mk:api`

> Attackers can use malicious AiScript to bypass API restrictions and access unauthorized endpoints like files or proxies via path traversal.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 May 2025
- **Updated:** 5 May 2025
- **Also known as:** GHSA-gmq6-738q-vjp2

## What is CVE-2025-46559?

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.

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-46559?

It affects 1 product.


Products: Misskey Misskey.

## How do I fix CVE-2025-46559?

No fix has been published for CVE-2025-46559 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-46559 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46559 exists.

## Other vulnerabilities in misskey-dev misskey

- [CVE-2025-25306](https://insights.sbomify.com/CVE-2025-25306/): Misskey's Incomplete Patch of CVE-2024-52591 Leads to Forgery of Federated Notes (critical 9.3)
- [CVE-2023-49079](https://insights.sbomify.com/CVE-2023-49079/): Misskey's missing signature validation allows arbitrary users to impersonate any remote user. (critical 9.3)
- [CVE-2026-28431](https://insights.sbomify.com/CVE-2026-28431/): Misskey lacks proper authorization checks and input validation (critical 9.2)
- [CVE-2023-52139](https://insights.sbomify.com/CVE-2023-52139/): Misskey vulnerable to improper authorization when accessing with third-party application (critical 9.1)
- [CVE-2024-52590](https://insights.sbomify.com/CVE-2024-52590/): Missing validation allows spoofed profiles in Misskey (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-46559 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46559 exists.

Affected product: misskey-dev misskey. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-46559/ (Markdown: https://insights.sbomify.com/CVE-2025-46559/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-46559
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-46559
- OSV: https://osv.dev/vulnerability/CVE-2025-46559

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-46559/
Summaries are generated and may contain mistakes; the official description above is the record.