CVE-2026-126803 json
Rote through 2.6.0 Privilege Escalation via Admin Settings API JWT Secret Exposure
published 13h ago modified 13h ago also EUVD-2026-124018
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- github.com/Rabithua/Rote@865d69f commit
- github.com/Rabithua/Rote#420 pull request
Is CVE-2026-126803 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.6 | CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 8.6 | CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Rabithua Rote
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
github.com
/Rabithua/Rote/pull/420
issue-tracking, patch
-
github.com
/Rabithua/Rote/commit/865d69fceb9c1f1a0d30923fae7cef072a38b22b
patch
-
github.com
/Rabithua/Rote/blob/v2.6.0/server/route/v2/admin.ts#L86-L146
technical-description
-
vul.yulun.ac.cn
/20261104/rote/
third-party-advisory
-
vulncheck.com
/advisories/rote-through-2.6.0-privilege-escalation-via-admin-settings-api-jwt-secret-exposure
third-party-advisory
Sources
- CVE List CVE-2026-126803
- NVD CVE-2026-126803
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.