Dozzle Agent Label-Based Access Control Bypass Allows Unauthorized Container Shell Access

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-24740: 0.42% estimated exploitation activity in the next 30 days; percentile 36.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A flaw in Dozzle’s agent-backed shell endpoints allows a user restricted by label filters (for example, label=env=dev) to obtain an interactive root shell in out‑of‑scope containers (for example, env=prod) on the same agent host by directly targeting their container IDs. Note: Tested on v9.0.2 likely affects all versions with agent mode support. Details When SIMPLE auth is enabled, Dozzle supports per‑user label filters in users.yaml (for example, filter: label=env=dev) to restrict which containers a user can see and interact with. These filters are propagated into the shell handlers, which resolve the target container via h.hostService.FindContainer(hostKey(r), id, userLabels) in both the attach and exec WebSocket endpoints, intending to limit shell access to containers within the user’s label scope. For agent-backed hosts, the corresponding implementation ignores the label scope when resolving a container by ID (agentservice.go#L27-L29): As a result, an authenticated user…

Published by the source

27 Jan 2026, 00:55 UTC

Last modified by the source

29 Jan 2026, 03:40 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m855-r557-5rc5

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

# Patch Next advisory brief: CVE-2026-24740

Advisory: Dozzle Agent Label-Based Access Control Bypass Allows Unauthorized Container Shell Access
IDs: CVE-2026-24740, GHSA-m855-r557-5rc5
Record: https://patchnext.com/advisories/cve-2026-24740 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
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.20260125230338-620e59aa2463. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/amir20/dozzle: affected < 1.29.1-0.20260125230338-620e59aa2463; fixed in 1.29.1-0.20260125230338-620e59aa2463

## 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://github.com/advisories/GHSA-m855-r557-5rc5 (GitHub-reviewed advisory GHSA-m855-r557-5rc5 lists affected ranges: Go github.com/amir20/dozzle >=0 <1.29.1-0.20260125230338-620e59aa2463)

Commands are suggestions: review each one before running it.