Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-45298: Unauthenticated SSRF in Dozzle Test Webhook

Published May 26, 2026 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.6High · v3.1
EPSS1.5%75th percentile
CISA KEVNoNot listed
In the wildReported36 exploitation records in Mallory
Vendor
Amirraminfar
IdentifiersCVE-2026-45298CWE-918 · Server-Side Request Forgery (SSRF)

CVE-2026-45298 is an unauthenticated server-side request forgery vulnerability in Dozzle versions earlier than 10.5.2. In documented default deployments where no authentication provider is configured, the test-webhook functionality accepts an attacker-controlled destination URL and request headers and passes them to the WebhookDispatcher, which issues an outbound HTTP POST. For targets returning a non-2xx status, Dozzle exposes the response status and returns up to 1 MB of the response body to the requester.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An unauthenticated remote attacker can cause the Dozzle host to send HTTP POST requests to attacker-selected destinations reachable from that host, including internal, loopback, link-local, and cloud-metadata services where network access permits. Attacker-controlled outbound headers may affect requests to those services. Reflection of non-2xx response bodies can enable internal service probing and disclosure of sensitive data accessible to Dozzle.

Mitigation

If you can’t patch tonight, do this now.

Until upgrade is complete, configure a supported Dozzle authentication provider and do not expose a default no-auth deployment to untrusted networks. Restrict access to the test-webhook functionality through reverse-proxy or firewall policy, limit access to trusted administrators, and apply egress filtering from the Dozzle host to prevent access to internal, loopback, link-local, and metadata-service destinations where feasible.

Remediation

Patch, then assume compromise.

Upgrade Dozzle to version 10.5.2 or later, which fixes the vulnerable behavior.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AmirraminfarDozzleapplication
FAQ

Frequently asked questions

Is CVE-2026-45298 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-45298?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2026-45298.
Is there a patch for CVE-2026-45298?
Upgrade Dozzle to version 10.5.2 or later, which fixes the vulnerable behavior.
What products are affected by CVE-2026-45298?
Amirraminfar Dozzle.
How severe is CVE-2026-45298?
CVE-2026-45298 has a CVSS v3.1 score of 8.6 (High) and an EPSS score of 1.5% (75th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.