CVE-2024-21635: Memos' Access Tokens Stay Valid after User Password Change
Summary Access Tokens are used 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. The bad actor though will still have access to their account because the bad actor's Access Token stays on the list as a valid token.
Published Nov 14, 2025 · Updated Mar 12, 2026
Affected packages
github.com/usememos/memos
- Ecosystem
- Go
- Affected
- <= 0.18.1
- Fixed in
- 0.18.2
- Check
go list -m github.com/usememos/memos
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Access Tokens are used 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.
The bad actor though 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.
Details
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. You can treat the old Access Tokens as "invalid" because those Access Tokens were created with the older password.
PoC
- Have 2 devices on hand
- Log onto your Memos account on both devices. Notice how Access Tokens are created for each.
- On one device, successfully change the password. Refresh the page on the 2nd device and notice how it doesn't log out the user.
- On the 2nd device, change the password again. Refresh the page on the 1st device and notice how it doesn't log out the user.
Impact
A bad actor will still have access to the user's account because the Access Token does not expire on a password update. Having multi-factor authentication will vastly improve account security in Account Takeover cases instead of just relying on a password.
Credited to jhademcconnell.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-6634
Memos has an Incorrect Privilege Assignment issue
low6.3No fixApr 20, 2026CVE-2025-65795
memos vulnerability allows the creation of arbitrary accounts
high7.5Dec 8, 2025CVE-2025-65796
memos vulnerability allows arbitrarily reactions deletion
medium4.3Dec 8, 2025CVE-2025-65797
memos vulnerability allows arbitrarily modification or deletion registered identity providers
medium6.5Dec 8, 2025CVE-2025-65798
memos vulnerability allows arbitrarily modification or deletion of attachments
medium5.4Dec 8, 2025CVE-2025-65799
memos lacks file name validation or verification
medium4.3Dec 8, 2025
