Read the docs
TI-2024-14360 Aliases CVE-2024-21635GHSA-mr34-8733-grr2

Memos Access Tokens Stay Valid after User Password Change

Priority MEDIUM 64CWE-287Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
None · High · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-287.

Summary

Memos is a privacy-first, lightweight note-taking service that uses Access Tokens to authenticate application access. When a user changes their password, the existing list of Access Tokens stay valid instead of expiring. If a user finds that their account has been compromised, they can update their password. In versions up to and including 0.18.1, though, the bad actor will still have access to their account because the bad actor's Access Token stays on the list as a valid token. The user will have to manually delete the bad actor's Access Token to secure their account. The list of Access Tokens has a generic Description which makes it hard to pinpoint a bad actor in a list of Access Tokens. A known patched version of Memos isn't available. To improve Memos security, all Access Tokens will need to be revoked when a user changes their password. This removes the session for all the user's devices and prompts the user to log in again. One can treat the old Access Tokens as "invalid" because those Access Tokens were created with the older password.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00307 23rd percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix Fixed github.com/usememos/memos (Go): 0.18.2

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
usememosmemosup to 0.18.1—No fix listedCNA
—github.com/usememos/memos (Go)before 0.18.20.18.2Patch availableGHSA-mr34-8733-grr2
  • memos Vendorusememos Affected up to 0.18.1 Fixed in — No fix listed CNA
  • github.com/usememos/memos (Go) Vendor— Affected before 0.18.2 Fixed in 0.18.2 Patch available GHSA-mr34-8733-grr2

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:usememos:memos:*:*:*:*:*:*:*:*up to 0.18.1Vulnerableusememos
  • cpe:2.3:a:usememos:memos:*:*:*:*:*:*:*:* Versions up to 0.18.1 Vulnerable ·usememos

Remediation

  • Fix · GHSA-mr34-8733-grr2 github.com/usememos/memos (Go) Fixed in 0.18.2 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2024-21635
  2. 2026-10-03 Alias added: GHSA-mr34-8733-grr2

References

Exploit 1

Advisory 1

Other 4

  • TI-2025-32234 The Memos application, up to version v0.24.3, allows for the embedding of markdown images… CVSS 3.1CRITICAL 9.8
  • TI-2025-16796 elestio memos v0.23.0 is vulnerable to Server-Side Request Forgery (SSRF) due to… CVSS 3.1CRITICAL 9.8
  • TI-2023-04328 Improper Access Control in usememos/memos CVSS 3.1CRITICAL 9.8
  • TI-2022-04459 Cross-site Scripting (XSS) - Stored in usememos/memos CVSS 3.1CRITICAL 9.0
  • TI-2022-04458 Cross-site Scripting (XSS) - Stored in usememos/memos CVSS 3.1CRITICAL 9.0
  • TI-2022-04283 Authorization Bypass Through User-Controlled Key in usememos/memos CVSS 3.1CRITICAL 9.8
See all 72 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences