Vulnerabilities

Memos before 0.27.0 contains a missing authorization vulnerability in the ActivityService ListActivities and GetActivity API methods that allows authenticated users to view all users' activity records.

Memos versions 0.26.0 through 0.30.0 fail to revoke refresh tokens when a user changes their password, allowing attackers to maintain account access.

Memos through 0.30.0 omits the 100.64.0.0/10 carrier-grade NAT address range from SSRF protection in its link-metadata fetcher, allowing unauthenticated attackers to bypass IP validation.

Memos' webhook dispatch function safeDialContext (internal/webhook/webhook.go) resolves the target hostname via net.DefaultResolver.LookupHost and validates the resulting IPs against reserved ranges, but then dials net.J…

Memos' webhook URL validation, isReservedIP (internal/webhook/validate.go), checks a candidate IP against a reservedCIDRs list that omits 0.0.0.0/8 and never calls ip.IsUnspecified — unlike the correctly implemented sibl…

A weakness has been identified in usememos memos up to 0.22.1.

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.

Incorrect access control in usememos memos v0.25.2 allows attackers with low-level privileges to arbitrarily modify or delete attachments made by other users.

Incorrect access control in the Identity Provider service of usememos memos v0.25.2 allows attackers with low-level privileges to arbitrarily modify or delete registered identity providers, leading to an account takeover…

Incorrect access control in usememos memos v0.25.2 allows attackers with low-level privileges to arbitrarily delete reactions made to other users' Memos.

Incorrect access control in the /api/v1/user endpoint of usememos memos v0.25.2 allows unauthorized attackers to create arbitrary accounts via a crafted request.

Memos is a privacy-first, lightweight note-taking service that uses Access Tokens to authenticate application access.

Memos 0.22 is vulnerable to Stored Cross site scripting (XSS) vulnerabilities by the upload attachment and user avatar features.

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.

The Memos application, up to version v0.24.3, allows for the embedding of markdown images with arbitrary URLs.

elestio memos v0.23.0 is vulnerable to Server-Side Request Forgery (SSRF) due to insufficient validation of user-supplied URLs, which can be exploited to perform SSRF attacks.

A stored cross-site scripting (XSS) vulnerability was discovered in usememos/memos version 0.9.1.

memos is a privacy-first, lightweight note-taking service.

memos is a privacy-first, lightweight note-taking service.

memos is a privacy-first, lightweight note-taking service.

memos is a privacy-first, lightweight note-taking service.

Cross-Site Request Forgery (CSRF) in GitHub repository usememos/memos prior to 0.15.1.

Improper Privilege Management in GitHub repository usememos/memos prior to 0.13.2.

Improper Input Validation in GitHub repository usememos/memos prior to 0.13.2.

Improper Access Control in GitHub repository usememos/memos prior to 0.13.2.