# CVE-2024-21635: GO-2025-4127 - Memos' Access Tokens Stay Valid after User Password Change in github.com/usememos/memos

Source: https://junglewise.ai/threats/cve-2024-21635-memos-access-tokens-stay-valid-after-user-password-change  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-11-14  
License: CC BY 4.0 with a link back

CVE-2024-21635 · Severity: high · CVSS 7.5 · Published 2025-11-14

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.

Technologies: [github.com/usememos/memos (Go)](https://junglewise.ai/threats/technologies/github-com-usememos-memos), [Usememos Memos](https://junglewise.ai/threats/technologies/memos). Vendors: [Go](https://junglewise.ai/threats/vendors/go), [Usememos](https://junglewise.ai/threats/vendors/usememos).

## Quick answers

**Is CVE-2024-21635 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2024-21635 being exploited in the wild.

**How severe is CVE-2024-21635?** High severity, with a CVSS score of 7.5, published 14 November 2025.

**Which products and versions are affected?** github.com/usememos/memos (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=0.18.2.

**Is there a fix for CVE-2024-21635?** Yes. github.com/usememos/memos (Go): upgrade to 0.18.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2024-21635?** Check whether you run github.com/usememos/memos (Go) or Usememos Memos at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/usememos/memos (Go): upgrade to 0.18.2 or later

  ```sh
  go get github.com/usememos/memos@v0.18.2
  ```


## Affected products

- github.com/usememos/memos (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=0.18.2
- Usememos Memos

## Identifiers

- CVE-2024-21635
- GHSA-mr34-8733-grr2
- GO-2025-4127

## Related threats

- [Memos missing authorization in ActivityService API methods](https://junglewise.ai/threats/cve-2026-113601-memos-before-0-27-0-contains-a-missing-authorization)
- [Memos link-metadata fetcher SSRF via missing carrier-grade NAT range](https://junglewise.ai/threats/cve-2026-82476-memos-link-metadata-fetcher-ssrf-via-missing-carrier-grade-nat)
- [usememos Memos SSO account takeover via identifier mismatch](https://junglewise.ai/threats/cve-2026-51584-usememos-memos-sso-account-takeover-via-identifier-mismatch)
- [Memos Server-Side Request Forgery in webhook validation](https://junglewise.ai/threats/cve-2026-51583-memos-server-side-request-forgery-in-webhook-validation)
- [usememos Memos HTML injection and UI redressing in SANITIZE_SCHEMA](https://junglewise.ai/threats/cve-2026-30586-usememos-memos-html-injection-and-ui-redressing-in-sanitize)