dbcve.org
DozzleApplication · Amirraminfar

CVE-2026-24740

CRITICAL · 9.9 CVSS v3.1 Published 2026-01-27
Fix available
A fix is available. Upgrade to 9.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Dozzle versions prior to 9.0.3 have an authorization bypass in agent-backed shell endpoints where label-based access controls can be circumvented by directly targeting container IDs, allowing users restricted to specific label scopes (e.g., env=dev) to obtain interactive root shells on out-of-scope containers (e.g., env=prod) running on the same agent host.

MitigationUpgrade Dozzle to version 9.0.3 or later to patch the authorization bypass. If immediate upgrade is not possible, restrict network access to agent endpoints and audit container ID access patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DozzleApplication
Affected:< 9.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Dozzle version
    Check the running Dozzle container or binary version using 'dozzle --version' or inspect the Docker container image tag
    Affected if version is present and less than 9.0.3
  2. Verify agent-backed shell feature is enabled
    Inspect Dozzle configuration or environment variables for agent-related settings (e.g., DOZZLE_AGENT_ENABLED, agent endpoints in the UI)
    Affected if agent-backed shell functionality is enabled in the Dozzle deployment
  3. Confirm label-based access controls are configured
    Check Dozzle configuration for label-based authorization rules (e.g., DOZZLE_LABEL_FILTER, env or label-specific access scopes in the config file)
    Affected if label-based access restrictions are defined to scope users to specific container labels
  4. Identify containers with different label scopes on the same agent host
    List all containers on the Dozzle agent host and examine their labels (e.g., 'docker ps --format "{{.Names}} {{.Labels}}"')
    Affected if multiple containers exist with different label values (e.g., env=dev vs env=prod) running on the same host where Dozzle agent is connected

You are affected if Dozzle version is below 9.0.3, agent-backed shell is enabled, label-based access controls are configured, and containers with different label scopes exist on the same agent host.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0.3 or later
Fixed in 9.0.3
Vendor patch github.com →
Interim mitigation

Upgrade Dozzle to version 9.0.3 or later to patch the authorization bypass. If immediate upgrade is not possible, restrict network access to agent endpoints and audit container ID access patterns.

Recommended fix High confidence

9.0.3

  1. Backup your current Dozzle configuration and data
  2. Pull the latest Dozzle image: docker pull amir20/dozzle:v9.0.3
  3. Stop the existing Dozzle container: docker stop <dozzle-container-id>
  4. Remove the old Dozzle container: docker rm <dozzle-container-id>
  5. Run a new Dozzle container with the same configuration but using the new image version 9.0.3
  6. Verify Dozzle starts successfully and the version is correct
  7. Test that the label filter restrictions are properly enforced

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dozzle Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24740 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24740 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data