https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 13:36:55 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-55499 <p>Cloudreve is a self-hosted file management and sharing system. Prior to 4.17.0, a single-file share event-stream subscription resolves the share root to the owner’s parent folder and subscribes to that folder topic, allowing an authenticated share recipient to receive names, paths, rename targets, event types, and hashed identifiers for unshared sibling files and folders. This issue is fixed in version 4.17.0.</p> <p>Cloudreve is a self-hosted file management and sharing system. Prior to 4.17.0, a single-file share event-stream subscription resolves the share root to the owner’s parent folder and subscribes to that folder topic, allowing an authenticated share recipient to receive names, paths, rename targets, event types, and hashed identifiers for unshared sibling files and folders. This issue is fixed in version 4.17.0.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-55499 https://vulnerability.circl.lu/vuln/ghsa-w8x7-h2px-xmq8 <p><strong>Affected:</strong> Go: github.com/cloudreve/Cloudreve/v4, Go: github.com/cloudreve/Cloudreve/v3</p> <p>## Summary When an authenticated recipient of a **single-file** share opens the file event stream (`GET /api/v4/file/events?uri=&lt;share-root&gt;`), 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&#39;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&#39;s parent folder that were never shared. Contents are not disclosed; file-activity metadata is.</p> <p>### Details ## Root cause (verified at `26b6b10`) **1. Events route — authenticated, feature-flagged, no share-scope check** (`routers/router.go`): ```go file := v4.Group(&#34;file&#34;); file.Use(middleware.RequiredScopes(types.ScopeFilesRead)) file.GET(&#34;events&#34;, middleware.LoginRequired(), middleware.IsFunctionEnabled(func(c *gin.Context) bool { return dep.SettingProvider().EventHubEnabled(c) }), controllers.FromQuery[explorer.ExplorerEventService](...), controllers.HandleExplorerEventsPush) ``` `EventHubEnabled` defaults `…</p> <p><strong>Affected:</strong> Go: github.com/cloudreve/Cloudreve/v4, Go: github.com/cloudreve/Cloudreve/v3</p> <p>## Summary When an authenticated recipient of a **single-file** share opens the file event stream (`GET /api/v4/file/events?uri=&lt;share-root&gt;`), 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&#39;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&#39;s parent folder that were never shared. Contents are not disclosed; file-activity metadata is.</p> <p>### Details ## Root cause (verified at `26b6b10`) **1. Events route — authenticated, feature-flagged, no share-scope check** (`routers/router.go`): ```go file := v4.Group(&#34;file&#34;); file.Use(middleware.RequiredScopes(types.ScopeFilesRead)) file.GET(&#34;events&#34;, middleware.LoginRequired(), middleware.IsFunctionEnabled(func(c *gin.Context) bool { return dep.SettingProvider().EventHubEnabled(c) }), controllers.FromQuery[explorer.ExplorerEventService](...), controllers.HandleExplorerEventsPush) ``` `EventHubEnabled` defaults `…</p> https://vulnerability.circl.lu/vuln/ghsa-w8x7-h2px-xmq8