CVE-2026-54560GHSA-VGJ4-345G-JCF8GO-2026-6022
Cloudreve: OAuth access tokens bypass scope enforcement due to missing client_id claim
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.16.1, 4.0.0-20260606015557-ed20843dc3df
- 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
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
Cloudreve is a self-hosted file management and sharing system. From 4.12.0 until 4.16.1, Cloudreve's OAuth access tokens are issued without the OAuth client_id claim, so the JWT verifier does not load token scopes into request context and RequiredScopes treats the request like non-scoped session authentication, allowing a low-scope OAuth access token to call APIs requiring higher scopes such as file, share, workflow, user setting, WebDAV account, and potentially admin scopes. This issue is fixed in version 4.16.1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- cloudreve cloudreve
From 4.12.0 · fixed in 4.16.1
- github.com/cloudreve/Cloudreve/v4Go
From 4.0.0-20260114075425-bc6845bd742c · fixed in 4.0.0-20260606015557-ed20843dc3df
- github.com/cloudreve/CloudreveGo
All versions
- github.com/cloudreve/Cloudreve/v3Go
All versions