cve.bz

CVE-2026-73087 amir20 dozzle: SSRF

2.3 lowEPSS 0.5%Fix available

Low (2.3) in amir20 dozzle. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/amir20/dozzle 1.29.1-0.20260804193351-8cf7ccd5ee04.

On this page
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.

Severity

CVSS 4.0

2.3 low
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-08-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-73087 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-73087?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-73087?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-73087 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
amir20 dozzle< 10.6.15

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-p2w3-6x73-2f6xGogithub.com/amir20/dozzle<1.29.1-0.20260804193351-8cf7ccd5ee041.29.1-0.20260804193351-8cf7ccd5ee04
GO-2026-6440Gogithub.com/amir20/dozzle<1.29.1-0.20260804193351-8cf7ccd5ee041.29.1-0.20260804193351-8cf7ccd5ee04

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20260916T180043-160000.1.1SUSE-SU-2026:23855-1 SUSE-SU-2026:23863-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260916T180043-160000.1.1openSUSE-SU-2026:21897-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON