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.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
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
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 | 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 include Usememos Memos.
How do I fix CVE-2025-65799?
Upgrade github.com/usememos/memos to 0.25.3 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
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 Memos has Cross-Site Scripting (XSS) Vulnerability in Image URLs
- CVE-2025-22952 Memos Server-Side Request Forgery (SSRF)
- CVE-2023-0109 Stored XSS in usememos/memos
- CVE-2023-4696 Improper Access Control in usememos/memos
- CVE-2022-4866 Cross-site Scripting (XSS) - Stored in usememos/memos
Sources
Also known as GHSA-qgjp-5g5x-vhq2, GO-2025-4218.