CVE
Rote through 2.6.0 Privilege Escalation via Admin Settings API JWT Secret Exposure
Affects Rote v1.0.0 through v2.6.0, where the attacker needs an account with the admin role. No fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- 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 v1.0.0 through v2.6.0 The attacker holds an account with the admin role
- 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, a product from Rabithua, has a privilege escalation flaw in versions through 2.6.0. An attacker who already has admin access over the network can read or overwrite the JWT signing secret through the admin settings API, then forge tokens for the super administrator to gain super_admin rights.
Read the original description
Rote through 2.6.0 contains a privilege escalation vulnerability that allows authenticated admins to obtain super_admin rights by reading or overwriting JWT signing secrets via /v2/api/admin/settings. Attackers can retrieve the unmasked jwtSecret from the security settings group and forge HS256 tokens for the super administrator to change user roles and escalate their own account.
Who should check
Teams running Rote v1.0.0 through v2.6.0 that have accounts with the admin role
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.6/10CVSS 8.6
- 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 v1.0.0 through v2.6.0 The attacker holds an account with the admin roleApply 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-126803 (Rote through 2.6.0 Privilege Escalation via Admin Settings API JWT Secret Exposure), 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-126803 (entry last updated 2026-11-11):
Affected:
- Rabithua Rote: through 2.6.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Rote versions v1.0.0 through v2.6.0 (source: https://vul.yulun.ac.cn/20261104/rote/)
- The attacker holds an account with the admin role (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, high-privilege login, no user action.
CISA KEV: CVE-2026-126803 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126803 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/admin.ts#L86-L146
- https://vul.yulun.ac.cn/20261104/rote/
- https://www.vulncheck.com/advisories/rote-through-2.6.0-privilege-escalation-via-admin-settings-api-jwt-secret-exposure
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-126803
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-126803"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Rabithua Rote
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-126803
Is CVE-2026-126803 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 authenticated admin can read or overwrite the JWT signing secret. With that secret, they can forge a token for the super admin and gain super_admin rights, which lets them change user roles.Source: vul.yulun.ac.cn, vulncheck.com
Which versions are affected by CVE-2026-126803?
Rote: through 2.6.0.Source: cve.now feed data
Am I affected, and how do I check?
Rote versions v1.0.0 through v2.6.0 are listed as affected. The issue requires an account with the admin role, so compare the installed Rote version against that range.Source: vul.yulun.ac.cn, vulncheck.com
How do I fix CVE-2026-126803?
The checked facts do not name a fixed version, so no upgrade target can be given. Until a fix is confirmed, limit admin-role accounts to those who need them.Source: vul.yulun.ac.cn, vulncheck.com