# CVE-2026-84203: Memos 0.26.0 through 0.30.0 Insufficient Session Expiration on Password Change

> Attackers with stolen refresh tokens maintain account access after password changes because Memos fails to revoke existing sessions.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-47v8-26mf-hw38

## What is CVE-2026-84203?

CVE-2026-84203 is a high-severity authentication bypass vulnerability in usememos memos, published on 1 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Memos versions 0.26.0 through 0.30.0 fail to revoke refresh tokens when a user changes their password, allowing attackers to maintain account access. An attacker with a stolen refresh token can call the RefreshToken RPC to obtain new access tokens and rotate the refresh token indefinitely, bypassing the password change security measure.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2026-84203?


## How do I fix CVE-2026-84203?

No fix has been published for CVE-2026-84203 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-84203 being exploited?

There is no known exploitation of CVE-2026-84203 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84203 and fix it if it is affected.

What it is: CVE-2026-84203 is a high-severity authentication bypass vulnerability in usememos memos, published on 1 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84203 in the wild and no public exploit code.

Affected product: usememos memos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84203/ (Markdown: https://insights.sbomify.com/CVE-2026-84203/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84203
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84203
- OSV: https://osv.dev/vulnerability/CVE-2026-84203

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84203/
Summaries are generated and may contain mistakes; the official description above is the record.