# CVE-2026-62286: Dozzle label filters do not restrict container event and statistics streams

> Authenticated restricted users can view unauthorized container telemetry and lifecycle events due to missing label filter enforcement on event streams.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-xcw9-qmmf-vqxj, GO-2026-6592

## What is CVE-2026-62286?

CVE-2026-62286 is a medium-severity missing authorization vulnerability in amir20 dozzle, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Dozzle is a realtime log viewer for docker containers. Prior to 10.6.7, streamEvents in internal/web/events.go applies a restricted user's label filter to container lists but not to the container-stat and container-event channels returned by GET /api/events/stream. In a simple-auth deployment using per-user filters, any authenticated restricted account can receive resource telemetry and lifecycle events for containers outside its authorized label scope. The exposed data includes container names, images, full label maps, CPU and memory use, network and disk totals, and deployment or restart activity across monitored hosts, but does not include log contents, environment values, or exec access. This issue is fixed in version 10.6.7.

Weakness: CWE-285 (Improper Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-62286?

3 open source packages ship an affected version, including github.com/amir20/dozzle.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/amir20/dozzle` | Go | All versions | 1.29.1-0.20260622172006-19c01e0fb491 |
| `github.com/amir20/dozzle` | Go | All versions | 1.29.1-0.20260622172006-19c01e0fb491 |
| `github.com/amir20/dozzle` | Go | All versions | 1.29.1-0.20260622172006-19c01e0fb491 |

## How do I fix CVE-2026-62286?

Upgrade github.com/amir20/dozzle to 1.29.1-0.20260622172006-19c01e0fb491 or later.

## Is CVE-2026-62286 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62286 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62286 and fix it if it is affected.

What it is: CVE-2026-62286 is a medium-severity missing authorization vulnerability in amir20 dozzle, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62286 exists.

Affected packages and fixed versions:
- github.com/amir20/dozzle (Go): affected all versions; fixed in 1.29.1-0.20260622172006-19c01e0fb491
- github.com/amir20/dozzle (Go): affected all versions; fixed in 1.29.1-0.20260622172006-19c01e0fb491
- github.com/amir20/dozzle (Go): affected all versions; fixed in 1.29.1-0.20260622172006-19c01e0fb491

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62286/ (Markdown: https://insights.sbomify.com/CVE-2026-62286/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62286
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62286
- OSV: https://osv.dev/vulnerability/CVE-2026-62286

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62286/
Summaries are generated and may contain mistakes; the official description above is the record.