CVE-2026-45298
Received Received - Intake
Webhook Test Endpoint Authentication Bypass in Dozzle

Publication date: 2026-05-26

Last updated on: 2026-05-26

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-26
Last Modified
2026-05-26
Generated
2026-05-27
AI Q&A
2026-05-27
EPSS Evaluated
N/A
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
dozzle dozzle to 10.5.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in Dozzle, a realtime log viewer for Docker containers, in versions prior to 10.5.2. In a default deployment without authentication configured, the POST endpoint /api/notifications/test-webhook can be accessed without any authentication.

An attacker can supply a URL to this endpoint, which the application then forwards to a WebhookDispatcher. This dispatcher sends an HTTP POST request to the attacker-controlled URL, including attacker-controlled request headers.

If the target URL responds with a non-2xx status code, the application returns both the response status code and up to 1MB of the response body back to the attacker.


How can this vulnerability impact me? :

This vulnerability can be exploited by an attacker to perform server-side request forgery (SSRF), allowing them to make the Dozzle server send HTTP POST requests to arbitrary URLs with attacker-controlled headers.

The attacker can receive detailed responses including status codes and up to 1MB of response data from the targeted URLs, potentially exposing sensitive internal services or data.

Because the endpoint is accessible without authentication, this can be exploited remotely and without any privileges, increasing the risk of information disclosure or further attacks on internal networks.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, upgrade Dozzle to version 10.5.2 or later, where the issue is fixed.

Additionally, avoid using the default deployment without authentication (i.e., do not leave DOZZLE_AUTH_PROVIDER unset) to prevent unauthorized access to the /api/notifications/test-webhook endpoint.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart