# CVE-2026-45298: Dozzle: Pre-auth SSRF with response-body reflection via POST /api/notifications/test-webhook (default no-auth deploy)

> Unauthenticated attackers can trigger server-side requests and read response bodies via the test-webhook endpoint in default Dozzle deployments.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-3v9w-6365-9w54, GO-2026-5101

## What is CVE-2026-45298?

CVE-2026-45298 is a high-severity server-side request forgery vulnerability in amir20 dozzle, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-45298?

3 open source packages ship an affected version, including github.com/amir20/dozzle. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/amir20/dozzle` | Go | All versions | None |
| `github.com/amir20/dozzle` | Go | All versions to 8.14.12 | None |
| `github.com/amir20/dozzle` | Go | All versions to 8.14.12 | None |

Products: Amirraminfar Dozzle.

## How do I fix CVE-2026-45298?

Upgrade to a fixed version.

## Is CVE-2026-45298 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45298 exists.

Public exploit code:

- Dozzle - Server Side Request Forgery (nuclei): http/cves/2026/CVE-2026-45298.yaml

## Other vulnerabilities in amir20 dozzle

- [CVE-2026-44985](https://insights.sbomify.com/CVE-2026-44985/): Dozzle: Cross-Site WebSocket Hijacking (CSWSH) on exec/attach endpoints bypasses authentication (high 8.7)
- [CVE-2026-24740](https://insights.sbomify.com/CVE-2026-24740/): Dozzle Agent Label-Based Access Control Bypass Allows Unauthorized Container Shell Access (high 8.7)
- [CVE-2024-47182](https://insights.sbomify.com/CVE-2024-47182/): Dozzle uses unsafe hash for passwords (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45298 and fix it if it is affected.

What it is: CVE-2026-45298 is a high-severity server-side request forgery vulnerability in amir20 dozzle, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45298 exists.

Affected packages and fixed versions:
- github.com/amir20/dozzle (Go): affected all versions; no fix listed
- github.com/amir20/dozzle (Go): affected all versions up to 8.14.12; no fix listed
- github.com/amir20/dozzle (Go): affected all versions up to 8.14.12; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45298/ (Markdown: https://insights.sbomify.com/CVE-2026-45298/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45298
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45298
- OSV: https://osv.dev/vulnerability/CVE-2026-45298

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45298/
Summaries are generated and may contain mistakes; the official description above is the record.