# CVE-2026-59262: AFFiNE - Unauthorized Document Edit History Access via GraphQL histories Field

> Authenticated users can access private document edit histories and sensitive user data by bypassing permission checks in the GraphQL API.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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:** 8 Jul 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-m4gp-5xh5-xhq4

## What is CVE-2026-59262?

CVE-2026-59262 is a high-severity missing authorization vulnerability in affine monorepo, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

AFFiNE's histories GraphQL field fails to validate Doc.Read permission before exposing document edit history, allowing authenticated workspace members to retrieve restricted content timelines. Attackers can supply arbitrary document GUIDs to access full edit histories including user names, emails, and timestamps of private pages they lack access to.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-59262 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59262 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59262 is a high-severity missing authorization vulnerability in affine monorepo, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59262 exists.

Affected product: affine monorepo. 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-59262/ (Markdown: https://insights.sbomify.com/CVE-2026-59262/index.md)
```

## Sources

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

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