Docker Sandboxes: contain code execution

At a glance

Docker Sandboxes: remote code execution. This 2026-09-16 case examines 1 version entries and 2 CVEs, documented releases and checks suited to runtime platforms, using CERTFR-2026-AVI-1189.

AI illustration: a dark cybersecurity technology space with restrained golden lighting Illustration · fictional scene
In this article

Retrospective for 2026-09-16, compiled on 27 October 2026. The date identifies the day being analysed; source publication and revision dates are recorded below.

What this advisory changes in your environment

The starting point is CERTFR-2026-AVI-1189, published on 2026-09-16. Its scope includes Docker Sandboxes. Reported consequences are remote code execution, data integrity compromise, loss of confidentiality. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.

This case focuses on Docker Sandboxes. Locate that edition in live installations, deployment images and actual dependencies, rather than treating every product from Docker as equivalent.

Products and versions to examine

Reference
CERTFR-2026-AVI-1189
Source first published
2026-09-16
Latest source revision available for this day
2026-09-16
Named components
Docker Sandboxes
CVE identifiers
CVE-2026-77179, CVE-2026-79994
ComponentPublished condition
Docker Sandboxes< 0.42.0

For Docker Sandboxes, the published condition is “< 0.42.0”. Compare the version actually loaded with that condition within its own release branch. A fix installed on another edition of Docker Sandboxes does not close this case.

Mechanism and prerequisites

Code execution can give an attacker the permissions of the affected process. Check the service account and reachable network destinations. Component isolation can reduce lateral movement opportunities, but does not replace the fix.

The primary record CVE-2026-77179, published by Docker, covers Docker Sandboxes. The retained revision is dated 2026-09-15. Its scope is presented separately from the integrations and product groupings in CERTFR-2026-AVI-1189.

The published metric for CVE-2026-77179 is CVSS 4.0, 9.4/10. The vector below describes technical prerequisites; it does not measure attack frequency or the likelihood that your deployment is compromised.

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

Attack vector
local
Prior privileges
none
User interaction
none
Complexity
low
Additional attack requirements
none
Weakness
CWE-59

Choose the appropriate intervention

  1. Locate Docker Sandboxes instances, running releases and service owners. Record condition < 0.42.0 in the ticket alongside reference CERTFR-2026-AVI-1189.
  2. Compare the installed branch with the vendor’s Docker Sandboxes release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
  3. After changing Docker Sandboxes, capture the loaded version again and verify the workflow below. Any exception needs an owner, an exposure-reduction measure and an expiry date.

Verify the fix in a real workflow

Validation scenario to adapt for Docker Sandboxes: For Docker Sandboxes, capture the version loaded by the process or active kernel, then restart only as required by maintenance instructions. Check a dependent workflow and look for embedded copies in distributed images or executables. This is a proposed defensive check, not a claim that testing was performed against third-party systems.

Limit of case CERTFR-2026-AVI-1189: this analysis replaces neither vendor prerequisites nor investigation of your logs. Only documented versions are reproduced; no attack date or victim is invented.

Questions specific to this case

Which condition should be checked for Docker Sandboxes?

Advisory CERTFR-2026-AVI-1189 states: Docker Sandboxes — < 0.42.0. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.

Which prerequisites does record CVE-2026-77179 specify?

For CVE-2026-77179, the published vector is CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H. Verify those conditions on Docker Sandboxes before applying them to an integration named in CERTFR-2026-AVI-1189.

Sources and related reading

Practical guide : Prioritize vulnerabilities and verify remediation

Explore the decision addressed in this case

Complete source advisory inventory

The article table may be an extract. These lists contain every affected-system entry and CVE in the specified advisory revision. They are not an inventory of your assets and do not map every CVE to every product.

Official source · CERTFR-2026-AVI-1189
Advisory revision : · Checked on :

Affected systems · 1

Original French wording is retained to avoid ambiguous translations of version conditions.

  1. Docker Sandboxes versions antérieures à 0.42.0
CVE identifiers · 2