CVE
Rote 1.2.0 through 2.6.0 Account Takeover via OAuth Account Merge Endpoint
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Rote versions 1.2.0 through 2.6.0 are affected. The target account has bound a GitHub or Apple account. The attacker holds any regular Rote account.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Rote, from vendor Rabithua, has an authorization bypass in its OAuth account merge endpoint that lets a logged-in user merge another user's OAuth-linked account into their own. This is reachable remotely by any user with a basic account, and an attacker could take over the victim's notes, attachments, and API keys and delete the victim's account.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
Who should check
Teams self-hosting Rabithua Rote 1.2.0 through 2.6.0 that use GitHub or Apple login bindings.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Rote versions 1.2.0 through 2.6.0 are affected. The target account has bound a GitHub or Apple account. The attacker holds any regular Rote account.Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126801 (Rote 1.2.0 through 2.6.0 Account Takeover via OAuth Account Merge Endpoint), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126801 (entry last updated 2026-11-11):
Affected:
- Rabithua Rote: from 1.2.0, through 2.6.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Rote versions 1.2.0 through 2.6.0 are affected. (source: https://vul.yulun.ac.cn/20261104/rote/)
- The target account has bound a GitHub or Apple account. (source: https://vul.yulun.ac.cn/20261104/rote/)
- The attacker holds any regular Rote account. (source: https://vul.yulun.ac.cn/20261104/rote/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126801 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126801 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Rabithua/Rote/pull/420
- https://github.com/Rabithua/Rote/commit/865d69fceb9c1f1a0d30923fae7cef072a38b22b
- https://github.com/Rabithua/Rote/blob/v2.6.0/server/route/v2/oauth.ts#L596-L659
- https://vul.yulun.ac.cn/20261104/rote/
- https://www.vulncheck.com/advisories/rote-1.2.0-through-2.6.0-account-takeover-via-oauth-account-merge-endpoint
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126801
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126801"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Rabithua Rote
From 1.2.0 · through 2.6.0
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Patch
- Patch
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126801
Is CVE-2026-126801 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An attacker holding any regular Rote account can take over a victim's account when the victim has bound a GitHub or Apple account. The takeover exposes the victim's notes, attachments and API keys, and lets the attacker delete the victim account.Source: vul.yulun.ac.cn, vulncheck.com
Which versions are affected by CVE-2026-126801?
Rote: from 1.2.0 through 2.6.0.Source: cve.now feed data
Am I affected, and how do I check?
Rote versions 1.2.0 through 2.6.0 are affected. The bug only applies when the target account has a GitHub or Apple account bound to it, so check your Rote version and whether OAuth login is linked to your account.Source: vul.yulun.ac.cn, vulncheck.com
How do I fix CVE-2026-126801?
No fixed version is listed in the checked facts, so no upgrade target can be named from them. Check the Rote project or advisory for a patched release beyond 2.6.0.Source: vul.yulun.ac.cn, vulncheck.com