Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

Cloudreve has Broken Access Control - Revoked Share Access Still Allows Signed File URL Generation via Cached context_hint

CVE-2026-101056GHSA-vx2m-jpxr-xv7w

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/cloudreve/Cloudreve/v3

    Affected
    every version
    Fixed in
    no fixed version recorded

  • Go github.com/cloudreve/Cloudreve

    Affected
    every version
    Fixed in
    no fixed version recorded

  • Go github.com/cloudreve/Cloudreve/v4

    Affected
    <= 4.0.0-20260606032813-26b6b1044b02
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-101056: 0.19% estimated exploitation activity in the next 30 days; percentile 9.23 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Cloudreve's file-listing responses hand the client a contexthint (UUID) that is meant to speed up follow-up operations. When that hint is replayed on the file/url (and file/thumb) routes, DBFS caches a shareNavigatorState containing the already-loaded share root and share row. On a later request carrying the same hint, shareNavigator.RestoreState repopulates shareRoot, and shareNavigator.To then skips Root. Root is the only place that re-checks inventory.IsValidShare (share expiry, remaining-download count, owner status, source-file validity) and the share password. As a result, a recipient who prewarms a context hint while access is valid can keep minting signed file URLs for already-known shared file paths for up to the context-hint TTL (5 60 = 300 s) after the owner deletes the share or the share expires — plus the lifetime of any signed entity URL minted in that window. This is a revocation / expiry bypass, not a way to discover unknown share contents: the attacker must…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-vx2m-jpxr-xv7w

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6287

  3. Revision 1 · created ·

    Published from osv record GHSA-vx2m-jpxr-xv7w

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-101056

Advisory: Cloudreve has Broken Access Control - Revoked Share Access Still Allows Signed File URL Generation via Cached context_hint
IDs: CVE-2026-101056, GHSA-vx2m-jpxr-xv7w
Record: https://patchnext.com/advisories/cve-2026-101056 (revision 3, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cloudreve/Cloudreve/v3: affected every version
- Go github.com/cloudreve/Cloudreve: affected every version
- Go github.com/cloudreve/Cloudreve/v4: affected <= 4.0.0-20260606032813-26b6b1044b02

## Suggested inspection (read-only)
- Go github.com/cloudreve/Cloudreve/v3: check the installed version with your package manager.
- Go github.com/cloudreve/Cloudreve: check the installed version with your package manager.
- Go github.com/cloudreve/Cloudreve/v4: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cloudreve/Cloudreve/v3, github.com/cloudreve/Cloudreve, github.com/cloudreve/Cloudreve/v4.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-vx2m-jpxr-xv7w (OSV record GHSA-vx2m-jpxr-xv7w lists affected ranges: Go github.com/cloudreve/Cloudreve/v4 >=0 <=4.0.0-20260606032813-26b6b1044b02)
- Verified: https://osv.dev/vulnerability/GO-2026-6287 (OSV record GO-2026-6287 lists affected ranges: Go github.com/cloudreve/Cloudreve >=0; Go github.com/cloudreve/Cloudreve/v3 >=0; Go github.com/cloudreve/Cloudreve/v4 >=0)
- Verified: https://github.com/advisories/GHSA-vx2m-jpxr-xv7w (GitHub-reviewed advisory GHSA-vx2m-jpxr-xv7w lists affected ranges: Go github.com/cloudreve/Cloudreve/v4 >=0 <=4.0.0-20260606032813-26b6b1044b02)

Commands are suggestions: review each one before running it.

Loading voting…