Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73087

SSRF (Server-Side Request Forgery) in github.com/amir20/dozzle (CVE-2026-73087)

Summary

SSRF in github.com/amir20/dozzle (CVE-2026-73087). Risk of unauthorized operations or information disclosure. Exploitable via isBlockedIP. Mitigation: upgrade to 1.29.1-0.20260804193351-8cf7ccd5ee04 or later.

Original description

The description as published by the source.

Summary

The isBlockedIP SSRF guard in Dozzle's webhook notification dispatcher blocks loopback, link-local, multicast, and unspecified addresses but does not recognize IPv6 transition mechanism addresses (RFC 3056 6to4, RFC 6052 NAT64, RFC 4380 Teredo) that embed arbitrary IPv4 addresses. An authenticated user can bypass the guard to reach loopback services, cloud metadata endpoints (169.254.169.254), and other blocked ranges via webhook notification URLs.

Affected component / versions

  • Package: github.com/amir20/dozzle
  • Affected versions: all versions with SSRF guard (current HEAD b9df313)
  • Vulnerable code: internal/notification/dispatcher/webhook.go

Details

Root cause (CWE-918)

internal/notification/dispatcher/webhook.go:32-51:

func isBlockedIP(ip net.IP) bool {
	if ip.IsLoopback() ||
		ip.IsLinkLocalUnicast() ||
		ip.IsLinkLocalMulticast() ||
		ip.IsMulticast() ||
		ip.IsInterfaceLocalMulticast() ||
		ip.IsUnspecified() {
		return true
	}
	if v4 := ip.To4(); v4 != nil && zeroNetV4.Contains(v4) {
		return true
	}
	if ip.Equal(net.IPv4bcast) {
		return true
	}
	return false
}

The guard intentionally allows RFC 1918 private ranges for self-hosted webhook targets, but blocks loopback (127.0.0.0/8, ::1), link-local (169.…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-73087 has been found in github.com/amir20/dozzle.
Attackers can target a specific entry point like isBlockedIP over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/amir20/dozzle to 1.29.1-0.20260804193351-8cf7ccd5ee04 or later.
If unsure, ask your IT team or search "github.com/amir20/dozzle CVE-2026-73087" on the vendor's site.

CVE-2026-73087 (github.com/amir20/dozzle) — CWE-918
Attack surface: isBlockedIP / b9df313 / false / safeDialContext
Patched: 1.29.1-0.20260804193351-8cf7ccd5ee04 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SSRF (CWE-918) exists in github.com/amir20/dozzle. Attackers reach the vulnerable code path via isBlockedIP.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/amir20/dozzle. Attack surface: isBlockedIP / b9df313 / false / safeDialContext.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.29.1-0.20260804193351-8cf7ccd5ee04.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/amir20/dozzle' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/amir20/dozzle' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/amir20/dozzle を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/amir20/dozzle to 1.29.1-0.20260804193351-8cf7ccd5ee04

    ステージング環境で 1.29.1-0.20260804193351-8cf7ccd5ee04 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/amir20/dozzle
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.29.1-0.20260804193351-8cf7ccd5ee04"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details