Dozzle versions before 11.1.2 contain a path traversal vulnerability in the log download endpoint. The issue arises because container display names are not properly sanitized when building ZIP archive entry names. This allows attackers who can label containers to craft path traversal sequences that write files outside the intended extraction directory when logs are downloaded and extracted.
Dozzle is a realtime log viewer for docker containers. Prior to 10.6.7, streamEvents in internal/web/events.go applies a restricted user'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.
Dozzle is a realtime log viewer for docker containers. From 10.5.2 until 10.6.15, the isBlockedIP SSRF guard in internal/notification/dispatcher/webhook.go, used by safeDialContext for webhook notification URLs, does not inspect IPv4 addresses embedded in 6to4, NAT64, Teredo, or IPv4-compatible IPv6 addresses, allowing an authenticated user to reach loopback or link-local targets that the guard intends to block. This issue is fixed in version 10.6.15.
Dozzle is a realtime log viewer for docker containers. Prior to 10.5.2, in a default dozzle deploy (the documented quickstart, no DOZZLE_AUTH_PROVIDER set), POST /api/notifications/test-webhook is reachable without authentication and forwards an attacker-controlled URL into a WebhookDispatcher that sends an HTTP POST to the supplied URL with attacker-controlled request headers, and returns the response status code AND up to 1MB of the response body to the caller, when the target replies non-2xx. This vulnerability is fixed in 10.5.2.
Dozzle versions prior to 10.5.2 contain an origin validation vulnerability in the WebSocket upgrader for the /exec and /attach endpoints. The CheckOrigin function accepts requests from any origin, combined with a JWT cookie set with SameSite: Lax, enabling Cross-Site WebSocket Hijacking (CSWSH). An attacker on a same-site origin can exploit this to gain interactive shell access to containers accessible by the victim. This vulnerability is fixed in version 10.5.2.
CVE-2026-24740 is a high-severity improper access control vulnerability in Dozzle, a realtime log viewer for Docker containers. Versions prior to 9.0.3 allow users restricted by label filters to bypass these restrictions and obtain an interactive root shell in containers outside their authorized scope by directly targeting container IDs. This flaw enables privilege escalation within the same host, potentially compromising container integrity and confidentiality. The vulnerability requires no user interaction and can be exploited remotely over the network with low complexity. Although no known exploits are currently in the wild, affected users should upgrade to Dozzle 9.0.3 immediately to mitigate risk. European organizations using Dozzle in containerized environments are at risk, especially those with multi-tenant or segmented container deployments.
