How many CVEs have patched validateFilename?

1 published CVEs changed validateFilename in usememos/memos, in 2 distinct patches totalling 15 changed lines, between 2025 and 2025.

What is the latest CVE that changed validateFilename?

CVE-2025-65799 (memos lacks file name validation or verification), published 2025-12-08, changed lines 710 to 724 of server/router/api/v1/attachment_service.go.

How does validateFilename compare to the rest of usememos/memos?

usememos/memos has 32 CVEs with a located fix in total; 1 of them changed validateFilename.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

usememos/memos

Function

validateFilename

Name: validateFilename in usememos/memos: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

server/router/api/v1/attachment_service.go

Last patched December 8, 2025

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

15

Lines changed

Added plus removed

2025

Years

By CVE publication date

Overview

validateFilename in usememos/memos was changed by 1 published CVE fixes in 2025, in 2 distinct patches that added or removed 15 lines in total.

usememos/memos has 32 CVEs with a located fix in total, so 3% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed validateFilename, newest first, with the lines each fix touched.

memos lacks file name validation or verification
CVE-2025-65799 · lines 710–724 · +15 −0
Medium · CVSS 4.3
EPSS 0.2%2025-12-08

Get an alert when the next CVE fix lands in usememos/memos, with the patched functions.

Monitor memos CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in usememos/memos changed by the most CVE fixes.

NewServer6 CVEs · server/server.go registerResourcePublicRoutes4 CVEs · server/resource.go redactIdentityProviderResponse4 CVEs · server/router/api/v1/idp_service.go DeleteIdentityProvider4 CVEs · server/router/api/v1/idp_service.go GetIdentityProvider4 CVEs · server/router/api/v1/idp_service.go ListIdentityProviders4 CVEs · server/router/api/v1/idp_service.go

All patched functions in usememos/memos

Frequently asked questions

Common questions about CVE fixes to validateFilename.

How many CVEs have patched validateFilename?: 1 published CVEs changed validateFilename in usememos/memos, in 2 distinct patches totalling 15 changed lines, between 2025 and 2025.
What is the latest CVE that changed validateFilename?: CVE-2025-65799 (memos lacks file name validation or verification), published 2025-12-08, changed lines 710 to 724 of server/router/api/v1/attachment_service.go.
How does validateFilename compare to the rest of usememos/memos?: usememos/memos has 32 CVEs with a located fix in total; 1 of them changed validateFilename.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track usememos/memos CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing