# CVE-2026-113601: Memos before 0.27.0 Missing Authorization via ActivityService ListActivities/GetActivity


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-599r-q6pw-w9jj

## What is CVE-2026-113601?

CVE-2026-113601 is a medium-severity vulnerability in usememos memos, published on 20 Oct 2026. 

### Official description

Memos before 0.27.0 contains a missing authorization vulnerability in the ActivityService ListActivities and GetActivity API methods that allows authenticated users to view all users' activity records. Low-privileged attackers can enumerate sequential activity IDs to obtain creator IDs, timestamps, and memo-comment references, including activity on other users' private memos.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-113601 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113601 is a medium-severity vulnerability in usememos memos, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113601 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-113601/ (Markdown: https://insights.sbomify.com/CVE-2026-113601/index.md)
```

## Sources

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

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