Vulnerability record

CVE-2019-5736

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record. Tracker snapshot: Aug 8, 2026.

What it is

Reported

runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, or (2) an existing container, to which the attacker previously had write access, that can be attached with docker exec. This occurs because of file-descriptor mishandling, related to /proc/self/exe. Source description excerpt; complete tracked detail loads below.

NVD published: Feb 12, 2019 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

What is affected

Reported

docker — docker. Product-level identification only; no affected-version conclusion is available from this field.

NVD published: Feb 12, 2019 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Urgency and basis

Reported

Act · 459.5

Tracker decision tier from the evidence detailed below · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Exploitation evidence

Reported

kev-listed · VulnCheck KEV

VulnCheck KEV added: Aug 25, 2022 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

What to do

Reported

Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Source remediation ↗

Tracked source remediation field · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Evidence detail

Loading the full tracker evidence record…