# CVE-2026-24740: Dozzle Agent Label-Based Access Control Bypass Allows Unauthorized Container Shell Access

> Attackers with restricted label access can bypass controls to gain root shell access in out-of-scope Docker containers on the same host.

- **Severity:** High 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`)
- **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:** 27 Jan 2026
- **Updated:** 28 Jan 2026
- **Also known as:** GHSA-m855-r557-5rc5, GO-2026-4380

## What is CVE-2026-24740?

CVE-2026-24740 is a high-severity missing authorization vulnerability in amir20 dozzle, published on 27 Jan 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 version 9.0.3, 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. Version 9.0.3 contains a patch for the issue.

Weakness: CWE-863 (Incorrect Authorization), CWE-284 (Improper Access Control)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/amir20/dozzle` | Go | All versions | 1.29.1-0.20260125230338-620e59aa2463 |
| `github.com/amir20/dozzle` | Go | All versions | 1.29.1-0.20260125230338-620e59aa2463 |
| `github.com/amir20/dozzle` | Go | All versions | 1.29.1-0.20260125230338-620e59aa2463 |

Products: Amirraminfar Dozzle.

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

Upgrade github.com/amir20/dozzle to 1.29.1-0.20260125230338-620e59aa2463 or later.

## Is CVE-2026-24740 being exploited?

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

## Other vulnerabilities in amir20 dozzle

- [CVE-2026-44985](https://insights.sbomify.com/CVE-2026-44985/): Dozzle: Cross-Site WebSocket Hijacking (CSWSH) on exec/attach endpoints bypasses authentication (high 8.7)
- [CVE-2026-45298](https://insights.sbomify.com/CVE-2026-45298/): Dozzle: Pre-auth SSRF with response-body reflection via POST /api/notifications/test-webhook (default no-auth deploy) (high 8.6)
- [CVE-2024-47182](https://insights.sbomify.com/CVE-2024-47182/): Dozzle uses unsafe hash for passwords (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24740 is a high-severity missing authorization vulnerability in amir20 dozzle, published on 27 Jan 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-24740 exists.

Affected packages and fixed versions:
- github.com/amir20/dozzle (Go): affected all versions; fixed in 1.29.1-0.20260125230338-620e59aa2463
- github.com/amir20/dozzle (Go): affected all versions; fixed in 1.29.1-0.20260125230338-620e59aa2463
- github.com/amir20/dozzle (Go): affected all versions; fixed in 1.29.1-0.20260125230338-620e59aa2463

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-24740/ (Markdown: https://insights.sbomify.com/CVE-2026-24740/index.md)
```

## Sources

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

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