Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.3amended

Dozzle: SSRF guard bypass via IPv6 transition addresses (6to4/NAT64/Teredo) in webhook notification dispatcher

CVE-2026-73087GHSA-p2w3-6x73-2f6x

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/amir20/dozzle 1.29.1-0.20260804193351-8cf7ccd5ee04), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.3 · 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 · score source
EPSS
  • CVE-2026-73087: 0.46% estimated exploitation activity in the next 30 days; percentile 40.31 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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: 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.254.0.0/16, fe80::/10), and other non-routable addresses. IPv6 transition mechanism addresses bypass all these…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-p2w3-6x73-2f6x

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6440

  4. Revision 1 · created ·

    Published from osv record GHSA-p2w3-6x73-2f6x

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73087

Advisory: Dozzle: SSRF guard bypass via IPv6 transition addresses (6to4/NAT64/Teredo) in webhook notification dispatcher
IDs: CVE-2026-73087, GHSA-p2w3-6x73-2f6x
Record: https://patchnext.com/advisories/cve-2026-73087 (revision 4, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/amir20/dozzle 1.29.1-0.20260804193351-8cf7ccd5ee04. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/amir20/dozzle: affected < 1.29.1-0.20260804193351-8cf7ccd5ee04; fixed in 1.29.1-0.20260804193351-8cf7ccd5ee04

## Suggested inspection (read-only)
- Go github.com/amir20/dozzle: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/amir20/dozzle.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-p2w3-6x73-2f6x (OSV record GHSA-p2w3-6x73-2f6x lists affected ranges: Go github.com/amir20/dozzle >=0 <1.29.1-0.20260804193351-8cf7ccd5ee04 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6440 (OSV record GO-2026-6440 lists affected ranges: Go github.com/amir20/dozzle >=0 <1.29.1-0.20260804193351-8cf7ccd5ee04 (fixed))
- Verified: https://github.com/advisories/GHSA-p2w3-6x73-2f6x (GitHub-reviewed advisory GHSA-p2w3-6x73-2f6x lists affected ranges: Go github.com/amir20/dozzle >=0 <1.29.1-0.20260804193351-8cf7ccd5ee04)

Commands are suggestions: review each one before running it.

Loading voting…