https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 22:44:46 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-62286 <p>Dozzle is a realtime log viewer for docker containers. Prior to 10.6.7, streamEvents in internal/web/events.go applies a restricted user&#39;s label filter to container lists but not to the container-stat and container-event channels returned by GET /api/events/stream. In a simple-auth deployment using per-user filters, any authenticated restricted account can receive resource telemetry and lifecycle events for containers outside its authorized label scope. The exposed data includes container names, images, full label maps, CPU and memory use, network and disk totals, and deployment or restart activity across monitored hosts, but does not include log contents, environment values, or exec access. This issue is fixed in version 10.6.7.</p> <p>Dozzle is a realtime log viewer for docker containers. Prior to 10.6.7, streamEvents in internal/web/events.go applies a restricted user&#39;s label filter to container lists but not to the container-stat and container-event channels returned by GET /api/events/stream. In a simple-auth deployment using per-user filters, any authenticated restricted account can receive resource telemetry and lifecycle events for containers outside its authorized label scope. The exposed data includes container names, images, full label maps, CPU and memory use, network and disk totals, and deployment or restart activity across monitored hosts, but does not include log contents, environment values, or exec access. This issue is fixed in version 10.6.7.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-62286 https://vulnerability.circl.lu/vuln/ghsa-xcw9-qmmf-vqxj <p><strong>Affected:</strong> Go: github.com/amir20/dozzle</p> <p>## Summary</p> <p>Dozzle supports per-user label filters in `users.yml` that are documented as an access-control boundary: &#34;Filters are used to restrict the containers that a user can see&#34; and &#34;the `guest` user can only see containers with the label `com.example.app` … useful for restricting access to specific containers&#34; (docs/guide/authentication.md). This is the mechanism operators use to give different users/tenants visibility into disjoint subsets of containers on the same host.</p> <p>The events stream handler `streamEvents` (GET `/api/events/stream`) honors that filter for the initial container list and for the incremental `containers-changed` updates, but it forwards two other channels — `container-stat` (live per-container CPU, memory, network and disk telemetry) and `container-event` (container lifecycle events: start/die/destroy/rename/pause/unpause, with the container&#39;s full attribute/label set) — to every authenticated client unconditionally, with no comparison against the caller&#39;s label filter. The upstream subscription `SubscribeEventsAndStats` fans out across every Docker client/host and never receives a label filter at all.</p> <p>As a result, any authenticated user — including one explicitly constrained to a single label scope — receives live resource telemetry for every container on every monitored host, plus lifecycle events carrying each container&#39;s name, image and complete label map. This crosses the exact isolation boundary the filter feature is documented to enforce. T…</p> <p><strong>Affected:</strong> Go: github.com/amir20/dozzle</p> <p>## Summary</p> <p>Dozzle supports per-user label filters in `users.yml` that are documented as an access-control boundary: &#34;Filters are used to restrict the containers that a user can see&#34; and &#34;the `guest` user can only see containers with the label `com.example.app` … useful for restricting access to specific containers&#34; (docs/guide/authentication.md). This is the mechanism operators use to give different users/tenants visibility into disjoint subsets of containers on the same host.</p> <p>The events stream handler `streamEvents` (GET `/api/events/stream`) honors that filter for the initial container list and for the incremental `containers-changed` updates, but it forwards two other channels — `container-stat` (live per-container CPU, memory, network and disk telemetry) and `container-event` (container lifecycle events: start/die/destroy/rename/pause/unpause, with the container&#39;s full attribute/label set) — to every authenticated client unconditionally, with no comparison against the caller&#39;s label filter. The upstream subscription `SubscribeEventsAndStats` fans out across every Docker client/host and never receives a label filter at all.</p> <p>As a result, any authenticated user — including one explicitly constrained to a single label scope — receives live resource telemetry for every container on every monitored host, plus lifecycle events carrying each container&#39;s name, image and complete label map. This crosses the exact isolation boundary the filter feature is documented to enforce. T…</p> https://vulnerability.circl.lu/vuln/ghsa-xcw9-qmmf-vqxj