Server-side Request Forgery (SSRF) Affecting github.com/amir20/dozzle/internal/notification/dispatcher package, versions <10.5.2
Threat Intelligence
This vulnerability is trending on Twitter; this may indicate a growing threat.
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-GOLANG-GITHUBCOMAMIR20DOZZLEINTERNALNOTIFICATIONDISPATCHER-17119839
- published2 Jun 2026
- disclosed27 May 2026
- creditEddie Ran
Introduced: 27 May 2026
CVE-2026-45298 (opens in a new tab)How to fix?
Upgrade github.com/amir20/dozzle/internal/notification/dispatcher to version 10.5.2 or higher.
Overview
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the POST /api/notifications/test-webhook endpoint, which is accessible without authentication in the default deployment. An attacker can cause the application to send HTTP POST requests to arbitrary URLs and retrieve the response status code and up to 1MB of the response body by supplying a crafted URL, potentially exposing sensitive information from internal services. This is only exploitable if the application is deployed without authentication (no DOZZLE_AUTH_PROVIDER set).