CVE-2026-45298
HighCVSS 8.6Exploitation Probability (EPSS)
Elevated risk71th percentile - higher than 71% of all known CVEs
Summary
In Dozzle before version 10.5.2, in the default configuration (no DOZZLE_AUTH_PROVIDER set), the POST /api/notifications/test-webhook endpoint is accessible without authentication. An attacker can supply an arbitrary URL, and Dozzle will send an HTTP POST with controlled headers and return the response (status code and up to 1MB of body) to the attacker.
Risk Assessment
The vulnerability allows using the Dozzle server as a proxy for SSRF attacks and potential leakage of data from internal server responses.
Recommendation
Upgrade Dozzle to version 10.5.2 or later, which contains the fix.
Other vulnerabilities in Dozzle
See all- CVE-2026-44985Critical
Cross-Site WebSocket Hijacking vulnerability in Dozzle prior to 10.5.2. The WebSocket upgrader for /exec and /attach endpoints accepts requests from any origin, and the JWT cookie uses SameSite: Lax. An attacker on the same site (e.g., a subdomain) can hijack the WebSocket session and gain interactive shell access to a container.
- CVE-2026-73087Low
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.
Original NVD description (English source)
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.