# CVE-2026-126801: Rote 1.2.0 through 2.6.0 Account Takeover via OAuth Account Merge Endpoint

> Authenticated Rote users can merge any OAuth-bound account into their own, taking over notes, attachments and API keys and deleting the victim account.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-5fvm-xr9w-32vj

## What is CVE-2026-126801?

CVE-2026-126801 is a high-severity missing authorization vulnerability in Rabithua Rote, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Rote 1.2.0 through 2.6.0 contains an authorization bypass in the OAuth bind/merge endpoint that allows authenticated users to merge any OAuth-bound account into their own. Attackers can submit a public existingUserId and GitHub or Apple user ID to take over notes, attachments, and API keys and delete the victim account.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

An affected version is exposed as installed. No special setting or call is needed.


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

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

## Is CVE-2026-126801 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126801 is a high-severity missing authorization vulnerability in Rabithua Rote, published on 11 Nov 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-126801 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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

## Sources

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

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