{"answers":{"affected":"3 open source packages ship an affected version, including github.com/usememos/memos. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-65799 in the wild and no public exploit code.","fix":"Upgrade github.com/usememos/memos to 0.25.3 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-65799 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2025-65799 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/usememos/memos (Go): affected all versions; fixed in 0.25.3\n- github.com/usememos/memos (Go): affected all versions; fixed in 0.25.3\n- github.com/usememos/memos (Go): affected all versions; fixed in 0.25.3\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-65799/ (Markdown: https://insights.sbomify.com/CVE-2025-65799/index.md)","id":"CVE-2025-65799","markdown":"https://insights.sbomify.com/CVE-2025-65799/index.md","name":"CVE-2025-65799","record":{"aliases":["GHSA-qgjp-5g5x-vhq2","GO-2025-4218"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Memos note-taking app","requires_auth":"low_privilege","summary":"Attackers can exploit missing file name validation in the attachment service to perform path traversal, potentially reading or modifying arbitrary files.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"memos","vendor":"usememos"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"}],"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"memos lacks file name validation or verification","id":"CVE-2025-65799","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":"usememos:memos","products":["usememos:memos"],"type":"path_traversal","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"Integer overflow in n/a","id":"CVE-2025-65803"},"packages":[{"ecosystem":"Go","fixed":["0.25.3"],"introduced":["0"],"last_affected":[],"package":"github.com/usememos/memos","purl":null,"source":"GHSA-qgjp-5g5x-vhq2"},{"ecosystem":"Go","fixed":["0.25.3"],"introduced":["0"],"last_affected":[],"package":"github.com/usememos/memos","purl":"pkg:golang/github.com/usememos/memos","source":"GHSA-qgjp-5g5x-vhq2"},{"ecosystem":"Go","fixed":["0.25.3"],"introduced":["0"],"last_affected":[],"package":"github.com/usememos/memos","purl":"pkg:golang/github.com/usememos/memos","source":"GO-2025-4218"}],"prev":{"headline":"memos vulnerability allows arbitrarily modification or deletion of attachments","id":"CVE-2025-65798"},"products":["n/a"],"published":"2025-12-08","related":[{"cvss_score":9.8,"headline":"Memos has Cross-Site Scripting (XSS) Vulnerability in Image URLs","id":"CVE-2025-50738","kev_date_added":null,"published":"2025-07-29"},{"cvss_score":9.8,"headline":"Memos Server-Side Request Forgery (SSRF)","id":"CVE-2025-22952","kev_date_added":null,"published":"2025-02-27"},{"cvss_score":9.8,"headline":"Stored XSS in usememos/memos","id":"CVE-2023-0109","kev_date_added":null,"published":"2024-11-15"},{"cvss_score":9.8,"headline":"Improper Access Control in usememos/memos","id":"CVE-2023-4696","kev_date_added":null,"published":"2023-09-01"},{"cvss_score":9.8,"headline":"Cross-site Scripting (XSS) - Stored in usememos/memos","id":"CVE-2022-4866","kev_date_added":null,"published":"2022-12-31"},{"cvss_score":9.8,"headline":"Improper Handling of Values in usememos/memos","id":"CVE-2022-4851","kev_date_added":null,"published":"2022-12-29"},{"cvss_score":9.8,"headline":"Improper Restriction of Excessive Authentication Attempts in usememos/memos","id":"CVE-2022-4797","kev_date_added":null,"published":"2022-12-28"}],"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":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can exploit missing file name validation in the attachment service to perform path traversal, potentially reading or modifying arbitrary files.","url":"https://insights.sbomify.com/CVE-2025-65799/"}