Information Disclosure in github.com/amir20/dozzle (CVE-2026-62286)
Summary
Vulnerability in github.com/amir20/dozzle (CVE-2026-62286). Risk of unauthorized operations or information disclosure. Exploitable via guest. Mitigation: upgrade to 1.29.1-0.20260622172006-19c01e0fb491 or later.
Original description
The description as published by the source.
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 upstream subscription SubscribeEventsAndStats fans out across every Docker client/host and never receives a label filter at all.
As a result, any authenticated user — including one explicitly constrained to a single label scope — receives live resource telemetry for every container on every monitored host, plus lifecycle events carrying each container's name, image and complete label map. This crosses the exact isolation boundary the filter feature is documented to enforce. Th…
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-62286 has been found in github.com/amir20/dozzle.
Attackers can target a specific entry point like guest over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade github.com/amir20/dozzle to 1.29.1-0.20260622172006-19c01e0fb491 or later.
If unsure, ask your IT team or search "github.com/amir20/dozzle CVE-2026-62286" on the vendor's site.
CVE-2026-62286 (github.com/amir20/dozzle) — CWE-200 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: guest / com.example.app / streamEvents / SubscribeEventsAndStats
Patched: 1.29.1-0.20260622172006-19c01e0fb491 — 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.
Information disclosure (CWE-200) exists in github.com/amir20/dozzle. Attackers reach the vulnerable code path via guest.
Check the vendor advisory for the affected versions of github.com/amir20/dozzle. Attack surface: guest / com.example.app / streamEvents / SubscribeEventsAndStats.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 1.29.1-0.20260622172006-19c01e0fb491.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/amir20/dozzle to 1.29.1-0.20260622172006-19c01e0fb491ステージング環境で 1.29.1-0.20260622172006-19c01e0fb491 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com