GHSA-78j5-8vq7-jxv5 CVE-2025-56760 GO-2025-3936
Memos Vulnerable to Path Traversal via the CreateResource Endpoint
Medium
Go
- Severity
- 4.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.35%
- Chance of exploitation in the next 30 days. Higher than 28.81% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-24 Path Traversal: '../filedir'
- Fix
- None yet
- No fixed version published
Description
When Memos 0.22 is configured to store objects locally, an attacker can create a file via the CreateResource endpoint containing a path traversal sequence in the name, allowing arbitrary file write on the server.
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/usememos/memos | <= 0.22.0 |
No fix yet |
| github.com/usememos/memos | all versions |
No fix yet |
How to fix
No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.
Severity breakdown
CVSS 3.1 4.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Weakness
CWE-24: Path Traversal: '../filedir'
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "../" sequences that can resolve to a location that is outside of that directory.
How to prevent it
- Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434. Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would b
- Implementation: Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-gqp3-hfc3-8q54 Memos has an Incorrect Privilege Assignment issue | Medium | Also affects github.com/usememos/memos |
| GHSA-qgjp-5g5x-vhq2 memos lacks file name validation or verification | Medium | Also affects github.com/usememos/memos |
| GHSA-99m2-qwx6-2w6f memos vulnerability allows arbitrarily modification or deletion registered identity providers | Medium | Also affects github.com/usememos/memos |
| GHSA-mg56-wc4q-rw4w memos vulnerability allows the creation of arbitrary accounts | High | Also affects github.com/usememos/memos |
| GHSA-8p44-g572-557h memos vulnerability allows arbitrarily modification or deletion of attachments | Medium | Also affects github.com/usememos/memos |
| GHSA-8jcj-g9f4-qx42 memos vulnerability allows arbitrarily reactions deletion | Medium | Also affects github.com/usememos/memos |
| GHSA-mr34-8733-grr2 Memos' Access Tokens Stay Valid after User Password Change | High | Also affects github.com/usememos/memos |
| GHSA-cgrg-86m5-xm4w Memos Vulnerable to Stored Cross-Site Scripting | Medium | Also affects github.com/usememos/memos |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor