# CVE-2025-65799: memos lacks file name validation or verification

> Attackers can exploit missing file name validation in the attachment service to perform path traversal, potentially reading or modifying arbitrary files.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Dec 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-qgjp-5g5x-vhq2, GO-2025-4218

## What is CVE-2025-65799?

CVE-2025-65799 is a medium-severity path traversal vulnerability in Usememos Memos, published on 8 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A lack of file name validation or verification in the Attachment service of usememos memos v0.25.2 allows attackers to execute a path traversal.

Weakness: CWE-73 (External Control of File Name or Path)

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

3 open source packages ship an affected version, including github.com/usememos/memos. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/usememos/memos` | Go | All versions | 0.25.3 |
| `github.com/usememos/memos` | Go | All versions | 0.25.3 |
| `github.com/usememos/memos` | Go | All versions | 0.25.3 |

Products: Usememos Memos.

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

Upgrade github.com/usememos/memos to 0.25.3 or later.

## Is CVE-2025-65799 being exploited?

There is no known exploitation of CVE-2025-65799 in the wild and no public exploit code.

## Other vulnerabilities in Usememos Memos

- [CVE-2025-50738](https://insights.sbomify.com/CVE-2025-50738/): Memos has Cross-Site Scripting (XSS) Vulnerability in Image URLs (critical 9.8)
- [CVE-2025-22952](https://insights.sbomify.com/CVE-2025-22952/): Memos Server-Side Request Forgery (SSRF) (critical 9.8)
- [CVE-2023-0109](https://insights.sbomify.com/CVE-2023-0109/): Stored XSS in usememos/memos (critical 9.8)
- [CVE-2023-4696](https://insights.sbomify.com/CVE-2023-4696/): Improper Access Control in usememos/memos (critical 9.8)
- [CVE-2022-4866](https://insights.sbomify.com/CVE-2022-4866/): Cross-site Scripting (XSS) - Stored in usememos/memos (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65799 is a medium-severity path traversal vulnerability in Usememos Memos, published on 8 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-65799 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/usememos/memos (Go): affected all versions; fixed in 0.25.3
- github.com/usememos/memos (Go): affected all versions; fixed in 0.25.3
- github.com/usememos/memos (Go): affected all versions; fixed in 0.25.3

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-65799/ (Markdown: https://insights.sbomify.com/CVE-2025-65799/index.md)
```

## Sources

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

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