Runc vulnerabilitiesRanked by how likely they are to be used.

Product29 versions
The short answer

Runc is made by Linuxfoundation. We track 12 published vulnerabilities in it, across 29 versions. None of them is on the list of flaws known to be exploited today. If you run Runc, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Runc vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Runc's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Runc flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 98%

    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...

    CVSS8.6Published11 Feb 2019
  2. 19%

    runc is a CLI tool for spawning and running containers on Linux according to the OCI specification.

    CVSS8.6Published31 Jan 2024
  3. 6.6%

    runc before 1.0.0-rc95 allows a Container Filesystem Breakout via Directory Traversal.

    CVSS8.5Published27 May 2021
  4. 4.4%

    runc through 1.0.0-rc8, as used in Docker through 19.03.2-ce and other products, allows AppArmor restriction bypass because libcontainer/rootfs_linux.go incorrectly checks mount targets, and thus a malicious Docker...

    CVSS7.5Published25 Sep 2019
  5. 1.8%

    runc is a CLI tool for spawning and running containers on Linux according to the OCI specification.

    CVSS5.0Published6 Dec 2021
  6. 0.5%

    Moby is an open-source project created by Docker to enable and accelerate software containerization.

    CVSS5.9Published24 Mar 2022
  7. 0.4%

    runc through 1.1.4 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go.

    CVSS7.0Published3 Mar 2023
  8. 0.4%

    runc through 1.0.0-rc9 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go.

    CVSS7.0Published12 Feb 2020
  9. 0.4%

    runc is a CLI tool for spawning and running containers on Linux according to the OCI specification.

    CVSS7.8Published17 May 2022
  10. 0.4%

    libcontainer/user/user.go in runC before 0.1.0, as used in Docker before 1.11.2, improperly treats a numeric UID as a potential username, which allows local users to gain privileges via a numeric username in the...

    CVSS7.8Published1 Jun 2016
Precursor Intelligence

Running Runc? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 12 published vulnerabilities listed under the name Runc, across 29 versions.

None of Runc's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Runc. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.