Cloudreve: Broken Access Control in file event stream: a single-file share recipient is subscribed to the owner's parent folder and receives activity events for unshared siblings
CVE-2026-55499GHSA-w8x7-h2px-xmq8
What to do
Partial vendor fix. 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.
Affected packages
Go github.com/cloudreve/Cloudreve/v3
- Affected
- <= 3.0.0-20250225100611-da4e44b77af4
- 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-20260613030215-0b00dd308f13
- Fixed in
- 4.0.0-20260613030215-0b00dd308f13
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6102 lists affected ranges: Go github.com/cloudreve/Cloudreve >=0; Go github.com/cloudreve/Cloudreve/v3 >=0; Go github.com/cloudreve/Cloudreve/v4 >=0 <4.0.0-20260613030215-0b00dd308f13 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-w8x7-h2px-xmq8 lists affected ranges: Go github.com/cloudreve/Cloudreve/v4 >=0 =0 <=3.0.0-20250225100611-da4e44b77af4
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2026-55499: 0.33% estimated exploitation activity in the next 30 days; percentile 26.33 (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 When an authenticated recipient of a single-file share opens the file event stream (GET /api/v4/file/events?uri=<share-root), Cloudreve validates the URI by listing it and then subscribes the caller to parent.ID(). For a single-file share, the share navigator resolves the bare share-root URI to the owner-side parent folder of the shared file (not the file), while the visible listing is filtered down to just the shared file. The event hub then keys topics by numeric file ID only and, on each file change, fans the event out to subscribers of every ancestor topic, filtering only the client ID that caused the event — never the subscriber's share scope. Consequently, a recipient of one shared file can receive Server-Sent Events (type, sibling path/name, rename target, hashed file ID) for other files and subfolders in the owner's parent folder that were never shared. Contents are not disclosed; file-activity metadata is. Details Root cause (verified at 26b6b10) 1. Events route —…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-w8x7-h2px-xmq8
- Revision 1 · created ·
Published from osv record GO-2026-6102
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-55499 Advisory: Cloudreve: Broken Access Control in file event stream: a single-file share recipient is subscribed to the owner's parent folder and receives activity events for unshared siblings IDs: CVE-2026-55499, GHSA-w8x7-h2px-xmq8 Record: https://patchnext.com/advisories/cve-2026-55499 (revision 2, source checked 26 Oct 2026, 15:27 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: github.com/cloudreve/Cloudreve/v4 4.0.0-20260613030215-0b00dd308f13. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/cloudreve/Cloudreve/v3: affected <= 3.0.0-20250225100611-da4e44b77af4 - Go github.com/cloudreve/Cloudreve: affected every version - Go github.com/cloudreve/Cloudreve/v4: affected < 4.0.0-20260613030215-0b00dd308f13; fixed in 4.0.0-20260613030215-0b00dd308f13 ## 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/GO-2026-6102 (OSV record GO-2026-6102 lists affected ranges: Go github.com/cloudreve/Cloudreve >=0; Go github.com/cloudreve/Cloudreve/v3 >=0; Go github.com/cloudreve/Cloudreve/v4 >=0 <4.0.0-20260613030215-0b00dd308f13 (fixed)) - Verified: https://github.com/advisories/GHSA-w8x7-h2px-xmq8 (GitHub-reviewed advisory GHSA-w8x7-h2px-xmq8 lists affected ranges: Go github.com/cloudreve/Cloudreve/v4 >=0 =0 <=3.0.0-20250225100611-da4e44b77af4) Commands are suggestions: review each one before running it.
Loading voting…