GHSA-mr34-8733-grr2

Source

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

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/11/GHSA-mr34-8733-grr2/GHSA-mr34-8733-grr2.json

JSON Data

https://api.osv.dev/v1/vulns/GHSA-mr34-8733-grr2

Aliases

Published

2025-11-14T22:09:54Z

Modified

2026-03-13T22:34:18.737252Z

Severity

7.1 (High) CVSS_V4 - 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 CVSS Calculator

Summary

Memos' Access Tokens Stay Valid after User Password Change

Details

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.

Database specific

{
    "cwe_ids": [
        "CWE-287"
    ],
    "nvd_published_at": "2025-11-14T15:15:48Z",
    "severity": "HIGH",
    "github_reviewed": true,
    "github_reviewed_at": "2025-11-14T22:09:54Z"
}

References

Affected packages

Go / github.com/usememos/memos

Package

Name: github.com/usememos/memos; View open source insights on deps.dev
Purl: pkg:golang/github.com/usememos/memos

Affected ranges

Type: SEMVER
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

0.18.2

Database specific

last_known_affected_version_range

"<= 0.18.1"

source

"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/11/GHSA-mr34-8733-grr2/GHSA-mr34-8733-grr2.json"