Alpine Linux Docker CVE-2026-92542

Cannot be determined from available data - the advisory only states that Docker is 'fixed in 29.8.2-r0' on Alpine Linux and provides no attack vector, privilege, or configuration detail. The one concrete prerequisite that can be stated is environmental: the target must be an Alpine Linux host running the Docker package at a revision earlier than 29.8.2-r0. Whether exploitation requires local access to the host, interaction with the Docker daemon/socket, a malicious image or container, specific daemon configuration, or authentication is NOT specified in the input and must be obtained from the upstream Docker/Moby CVE and the Alpine security database before defenders can assess realistic exposure.

This entry provides almost no technical signal to assess real-world risk. The only data present is an Alpine Linux advisory-style string ('docker fixed in 29.8.2-r0') and a reporter of 'vendor:alpine' - there is no CVSS score, no CVSS vector, no CWE, and no description of the vulnerability class, attack vector, or impact. As a result, none of the standard prioritization signals can be evaluated: attack vector, complexity, and privilege requirements are all unknown; there is no EPSS probability provided; KEV status is not indicated (treat as not listed); no POC is referenced; and no SSVC exploitation/automatable/technical-impact values are available. Exploitation status is therefore 'no public exploit identified at time of analysis.' The one meaningful risk amplifier is prevalence: Docker Engine is ubiquitously deployed across development, CI/CD, and production container hosts, so ANY genuine Docker Engine vulnerability has a very large attack surface. However, with the actual flaw undescribed it is impossible to distinguish a high-priority container-escape/privilege-escalation issue from a low-severity local or informational bug. This must be treated as an incomplete record: the affected component (Docker, as packaged by Alpine) and the fixed version (29.8.2-r0) are the only confirmed facts, and a vendor advisory (Alpine secdb / the upstream Moby/Docker CVE) should be consulted before any prioritization decision.

No exploit scenario can be responsibly constructed because the vulnerability class, attack vector, and impact are not described in the available data. In general terms, an attacker or malicious container/image would interact with the Docker daemon on an Alpine host running a version prior to 29.8.2-r0, but the specific trigger and outcome are unknown. No POC is referenced in the input.