dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-54560

HIGH · 7.6 CVSS v3.1 Published 2026-07-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
80/100
Remediation priority · High
Remotely reachable Patch available 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cloudreve versions 4.12.0-4.16.1 issue OAuth access tokens without the client_id claim, causing the JWT verifier to not load token scopes into request context. The RequiredScopes middleware incorrectly treats these tokens as non-scoped session authentication, allowing low-scope OAuth tokens to bypass authorization and access APIs requiring higher scopes including file, share, workflow, user settings, WebDAV accounts, and potentially admin APIs.

MitigationUpgrade to Cloudreve version 4.16.1 or later where the OAuth client_id claim is properly included in tokens and scopes are correctly loaded into request context for authorization.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Cloudreve version
    Check the Cloudreve version by reviewing the application binary, Docker image tag, or the admin dashboard version information. This is typically found in the footer of the web interface or by querying the API endpoint /api/v3/user/me/info
    Affected if The version is 4.12.0, 4.13.0, 4.14.0, 4.15.0, 4.16.0, or 4.16.1
  2. Determine if OAuth authentication is in use
    Review Cloudreve configuration for OAuth provider settings in config.yml or equivalent. Check if OAuth clients have been registered and are being used for API authentication instead of session-based authentication
    Affected if OAuth providers are configured and OAuth access tokens are being used to authenticate API requests
  3. Inspect OAuth token claims
    Decode a sample OAuth access token (JWT format) and verify whether the client_id claim is present. Use a JWT decoder tool or command line to examine the token payload
    Affected if The OAuth token payload is missing the client_id claim, indicating tokens were issued by an affected version
  4. Verify API access pattern
    Review API access logs or audit trails to identify if OAuth tokens are being used to call APIs that require elevated scopes such as file operations, share management, workflow execution, user settings modifications, WebDAV account management, or administrative functions
    Affected if OAuth tokens are accessing high-scope APIs while carrying only limited scopes due to the client_id claim being absent

A user is affected if Cloudreve version is between 4.12.0 and 4.16.1, OAuth authentication is enabled, and OAuth tokens are being used to access APIs that require scopes higher than what the token actually possesses due to the missing client_id claim in token payloads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Cloudreve version 4.16.1 or later where the OAuth client_id claim is properly included in tokens and scopes are correctly loaded into request context for authorization.

Recommended fix High confidence

4.16.1

  1. Obtain the latest Cloudreve 4.16.1 release from the official Cloudreve repository
  2. Back up your current Cloudreve installation and database
  3. Stop the running Cloudreve service
  4. Replace the Cloudreve binary/application files with version 4.16.1
  5. Review any updated configuration requirements in the release notes
  6. Start the Cloudreve service and verify it operates normally
  7. Test that OAuth authentication works correctly with the new version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54560 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54560 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data