Security readout for executives and security teams
Plain-English summary
Dozzle versions before 9.0.3 can let a logged-in user bypass container label restrictions and open a root shell in containers they should not access. This matters most where Dozzle agents are used to separate access between environments, such as dev and production, on the same host.
Executive priority
Treat as high priority if Dozzle is used to manage production containers or enforce environment separation. An authenticated low-privilege user could cross boundaries and gain powerful container access. Patch promptly, starting with shared agent hosts.
Technical view
CVE-2026-24740 affects amir20/dozzle before 9.0.3. The agent-backed shell endpoints do not properly enforce label-based access controls, allowing a low-privileged authenticated user constrained by filters to target out-of-scope container IDs on the same agent host. The issue is mapped to CWE-284 and CWE-863, with CVSS 4.0 score 8.7.
Likely exposure
Exposure is likely in Dozzle deployments before 9.0.3 that use agents, interactive shell access, and label filters for authorization boundaries. Risk is higher when multiple trust zones share an agent host.
Exploitation context
The CVE requires authenticated access but no user interaction. The source bundle does not show CISA KEV listing or public active exploitation evidence. The business impact is unauthorized privileged shell access to containers outside the user’s assigned scope.
Researcher notes
The advisory describes an authorization bypass in agent shell handling, not a remote unauthenticated issue. Validation should focus on version, agent topology, label-filtered access policies, and shell endpoint exposure. Avoid assuming compromise without corroborating logs or detections.
Mitigation direction
- Upgrade Dozzle to version 9.0.3 or later.
- Prioritize agent deployments using label filters for access separation.
- Limit Dozzle access to trusted users until upgraded.
- Review vendor advisory and release notes for deployment-specific guidance.
Validation and detection
- Inventory all Dozzle instances and record versions.
- Confirm whether Dozzle agents and shell endpoints are enabled.
- Identify users restricted by label filters.
- Verify affected instances are upgraded to 9.0.3 or later.
- Review access logs for unexpected shell activity against out-of-scope containers.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-24740 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: 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
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/amir20/dozzle/security/advisories/GHSA-m855-r557-5rc5CVE reference · x_refsource_CONFIRM
- https://github.com/amir20/dozzle/commit/620e59aa246347ba8a27e68c532853b8a5137bc1CVE reference · x_refsource_MISC
- https://github.com/amir20/dozzle/releases/tag/v9.0.3CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.