Skip to content
CVE-2026-126801: OAuth Bypass Vulnerability in Rote Affects User Accounts

CVE-2026-126801: OAuth Bypass Vulnerability in Rote Affects User Accounts

First seen 12 Nov 2026, 16:49 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 12, 2026 at 16:50 UTC
  • •CVE-2026-126801 allows account takeover via OAuth merge in Rote versions 1.2.0-2.6.0.
  • •Attackers can exploit this vulnerability without user interaction, posing a high risk.
  • •Organizations should prioritize upgrading to patched versions and monitor OAuth activity.

A high-impact vulnerability, CVE-2026-126801, has been identified in Rote versions 1.2.0 through 2.6.0, allowing authenticated users to exploit an authorization bypass in the OAuth bind/merge endpoint. This flaw enables attackers to merge any OAuth-bound account into their own, potentially leading to account takeover and data loss. The vulnerability affects users who utilize OAuth sign-in with GitHub or Apple, particularly in internet-accessible deployments. Attackers can execute this without user interaction, making it a significant risk for organizations with sensitive data. The urgency for exploitation cannot be confirmed as there are no details on KEV, SSVC, PoC, or EPSS status. Organizations are advised to monitor for unusual OAuth requests and review authentication logs. Prompt upgrades to patched versions are recommended to mitigate risks.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-11
CVE-2026-126801 published
The vulnerability was officially published with a CVSS score of 8.7, indicating high severity.
Redpacketsecurity
2026-11-12
Vulnerability details disclosed
Redpacketsecurity and Vulncheck provided detailed analysis of the OAuth bypass vulnerability and its implications.
Vulncheck

More articles in this cluster (4)

Following this threat?

Track CVE-2026-126801 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which versions of Rote are affected?
Rote versions 1.2.0 through 2.6.0 are affected by CVE-2026-126801.
What should organizations do to mitigate this vulnerability?
Organizations should upgrade to a patched version of Rote and monitor for unusual OAuth activity.
Is there any confirmed exploitation of this vulnerability?
The articles do not confirm any active exploitation of CVE-2026-126801 at this time.