CVE-2019-5736

HIGHNVD 8.69.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 99% probability of exploitation within the next 30 days (top 0.1% of all CVEs). NVD baseline CVSS 8.6 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Trending — 4 sources updated this weekWeaponized
8.6
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 99%
CISA-KEV: Not listedEPSS: 99%CVSS: 8.6Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.6
EG Score
9.0(high)
EG Risk
84(Track)
EG Risk 84/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation99% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.9%
KEV
Not listed

Published

February 11, 2019

Last Modified

November 21, 2024

References (132)

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuvim-syntax-docker (18.09.7-0ubuntu1~18.10.3) @ cosmic2026-05-23ubuntu
redhatcontainer-tools:rhel8-8000020190416221845.2ffa3d272019-05-07redhat
redhatdocker-2:1.12.6-79.git5680db5.el72019-02-26redhat
redhatpatch2019-02-25redhat
redhatrunc-0:1.0.0-59.dev.git2abd837.el72019-02-11redhat
redhatdocker-2:1.13.1-91.git07f3374.el72019-02-11redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(7)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:46 UTCEG score recompute
  2. 2026-07-22 21:29 UTCEG score recompute▲ 0.40
  3. 2026-07-22 21:29 UTCVendor advisory
  4. 2026-07-22 21:29 UTCGHSA enrichment
  5. 2026-07-19 14:28 UTCEPSS rescore
  6. 2026-07-19 14:28 UTCEPSS rescore
  7. 2026-07-12 19:38 UTCOSV refresh
  8. 2026-07-06 16:25 UTCEPSS rescore
  9. 2026-07-06 16:25 UTCEPSS rescore
  10. 2026-06-24 04:59 UTCOSV refresh
  11. 2026-06-23 21:31 UTCEPSS rescore
  12. 2026-06-23 21:31 UTCEPSS rescore
  13. 2026-06-18 17:50 UTCEPSS rescore
  14. 2026-06-18 17:50 UTCEPSS rescore
  15. 2026-06-15 17:46 UTCEPSS rescore
  16. 2026-06-14 23:15 UTCEPSS rescore
  17. 2026-06-14 23:15 UTCEPSS rescore
  18. 2026-06-12 23:09 UTCEPSS rescore
  19. 2026-06-12 23:09 UTCEPSS rescore
  20. 2026-06-11 13:58 UTCEPSS rescore
  21. 2026-06-10 22:16 UTCEPSS rescore
  22. 2026-06-10 22:16 UTCEPSS rescore
  23. 2026-06-08 14:15 UTCEPSS rescore
  24. 2026-06-08 14:15 UTCEPSS rescore
  25. 2026-06-08 14:15 UTCEPSS rescore
Show 20 more
  1. 2026-06-07 15:23 UTCEPSS rescore
  2. 2026-06-07 15:23 UTCEPSS rescore
  3. 2026-06-07 09:30 UTCOSV refresh
  4. 2026-06-06 13:45 UTCEPSS rescore
  5. 2026-06-06 13:45 UTCEPSS rescore
  6. 2026-06-05 22:45 UTCEPSS rescore
  7. 2026-06-05 06:08 UTCEPSS rescore
  8. 2026-06-02 20:11 UTCEPSS rescore
  9. 2026-06-02 20:11 UTCEPSS rescore
  10. 2026-06-01 13:50 UTCEPSS rescore
  11. 2026-06-01 13:50 UTCEPSS rescore
  12. 2026-05-31 00:14 UTCEPSS rescore
  13. 2026-05-31 00:14 UTCEPSS rescore
  14. 2026-05-29 13:42 UTCEPSS rescore
  15. 2026-05-28 13:43 UTCEPSS rescore
  16. 2026-05-28 13:43 UTCEPSS rescore
  17. 2026-05-24 16:47 UTCEPSS rescore
  18. 2026-05-23 02:49 UTCEG score recompute
  19. 2026-05-23 02:49 UTCVendor advisory
  20. 2026-05-23 02:49 UTCGHSA enrichment

Publicly available exploits

(9 references)

Working exploit code is in the public domain (1 Metasploit module) (6 GitHub PoCs) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCepsteina16/Docker-Escape-Miner
    First seen Dec 12, 2019

    Code sample for using exploit CVE-2019-5736 to mine bitcoin with no association to original container or user.

    Open source ↗
  • GitHub PoCtwistlock/RunC-CVE-2019-5736
    First seen Feb 20, 2019

    CVE-2019-5736 POCs

    Open source ↗
  • GitHub PoCagppp/cve-2019-5736-poc
    First seen Feb 15, 2019

    getshell test

    Open source ↗
  • GitHub PoCjas502n/CVE-2019-5736
    First seen Feb 14, 2019

    runc容器逃逸漏洞预警

    Open source ↗
  • Exploit-DBEDB-46369
    First seen Feb 13, 2019

    runc < 1.0-rc6 (Docker < 18.09.2) - Container Breakout (2)

    Open source ↗
  • GitHub PoCFrichetten/CVE-2019-5736-PoC
    First seen Feb 13, 2019

    PoC for CVE-2019-5736

    Open source ↗
  • Exploit-DBEDB-46359
    First seen Feb 12, 2019

    runc < 1.0-rc6 (Docker < 18.09.2) - Container Breakout (1)

    Open source ↗
  • GitHub PoCq3k/cve-2019-5736-poc
    First seen Feb 12, 2019

    Unweaponized Proof of Concept for CVE-2019-5736 (Docker escape)

    Open source ↗
  • Metasploitexploit/linux/local/docker_runc_escape✓ verified
    First seen Jan 1, 2019

    Docker Container Escape Via runC Overwrite

    Open source ↗

Frequently asked(5)

What is CVE-2019-5736?
CVE-2019-5736 is a high vulnerability published on February 11, 2019. 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…
When was CVE-2019-5736 disclosed?
CVE-2019-5736 was first published in the National Vulnerability Database on February 11, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-5736 actively exploited?
CVE-2019-5736 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-5736?
CVE-2019-5736 has a CVSS v3 base score of 8.6 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2019-5736?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-5736, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-5736

Explore →

Is Your Infrastructure Affected by CVE-2019-5736?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs