Skip to main content
VulnerabilityPublished Updated

CVE-2026-62286: amir20 dozzle · Information Exposure

Affects amir20 dozzleSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 10.6.7 when convenient.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.6.7
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade dozzle and amir20/dozzle to 10.6.7.

Affected software

ProductAffectedFixed in
amir20dozzleAffected
  • <10.6.7
Fixed in
  • 10.6.7
GitHubamir20/dozzlepkg:github/amir20/dozzleOther threatsAffected
  • <10.6.7
Fixed in
  • 10.6.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade amir20 dozzle to version 10.6.7 or later, where this issue is fixed. No other mitigation is required as the vendor has provided an official fix.

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.

References

Community reviews

Loading reviews…