Skip to content

← Actionable
Medium, CVSS 4.3amended

Dozzle label filters do not restrict container event and statistics streams

CVE-2026-62286GHSA-xcw9-qmmf-vqxj

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.20260622172006-19c01e0fb491), 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.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-62286: 0.43% estimated exploitation activity in the next 30 days; percentile 36.80 (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 Dozzle supports per-user label filters in users.yml that are documented as an access-control boundary: "Filters are used to restrict the containers that a user can see" and "the guest user can only see containers with the label com.example.app … useful for restricting access to specific containers" (docs/guide/authentication.md). This is the mechanism operators use to give different users/tenants visibility into disjoint subsets of containers on the same host. The events stream handler streamEvents (GET /api/events/stream) honors that filter for the initial container list and for the incremental containers-changed updates, but it forwards two other channels — container-stat (live per-container CPU, memory, network and disk telemetry) and container-event (container lifecycle events: start/die/destroy/rename/pause/unpause, with the container's full attribute/label set) — to every authenticated client unconditionally, with no comparison against the caller's label filter. The…

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

    Amended from ghsa record GHSA-xcw9-qmmf-vqxj

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6592

  3. Revision 1 · created ·

    Published from osv record GHSA-xcw9-qmmf-vqxj

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-62286

Advisory: Dozzle label filters do not restrict container event and statistics streams
IDs: CVE-2026-62286, GHSA-xcw9-qmmf-vqxj
Record: https://patchnext.com/advisories/cve-2026-62286 (revision 3, 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: Medium (CVSS 4.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.20260622172006-19c01e0fb491. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/amir20/dozzle: affected < 1.29.1-0.20260622172006-19c01e0fb491; fixed in 1.29.1-0.20260622172006-19c01e0fb491

## 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/GO-2026-6592 (OSV record GO-2026-6592 lists affected ranges: Go github.com/amir20/dozzle >=0 <1.29.1-0.20260622172006-19c01e0fb491 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-xcw9-qmmf-vqxj (OSV record GHSA-xcw9-qmmf-vqxj lists affected ranges: Go github.com/amir20/dozzle >=0 <1.29.1-0.20260622172006-19c01e0fb491 (fixed))
- Verified: https://github.com/advisories/GHSA-xcw9-qmmf-vqxj (GitHub-reviewed advisory GHSA-xcw9-qmmf-vqxj lists affected ranges: Go github.com/amir20/dozzle >=0 <1.29.1-0.20260622172006-19c01e0fb491)

Commands are suggestions: review each one before running it.

Loading voting…