runc can be confused to create empty files/directories on the host

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

4.8 · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N/U:Green · score source

EPSS

• CVE-2024-45310: 0.32% estimated exploitation activity in the next 30 days; percentile 24.70 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact runc 1.1.13 and earlier as well as 1.2.0-rc2 and earlier can be tricked into creating empty files or directories in arbitrary locations in the host filesystem by sharing a volume between two containers and exploiting a race with os.MkdirAll. While this can be used to create empty files, existing files will not be truncated. An attacker must have the ability to start containers using some kind of custom volume configuration. Containers using user namespaces are still affected, but the scope of places an attacker can create inodes can be significantly reduced. Sufficiently strict LSM policies (SELinux/Apparmor) can also in principle block this attack -- we suspect the industry standard SELinux policy may restrict this attack's scope but the exact scope of protection hasn't been analysed. This is exploitable using runc directly as well as through Docker and Kubernetes. The CVSS score for this vulnerability is CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N (Low severity, 3.6).…

Published by the source

3 Sep 2024, 19:49 UTC

Last modified by the source

21 Feb 2025, 21:03 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jfvp-7x6p-h2pv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-45310

Advisory: runc can be confused to create empty files/directories on the host
IDs: CVE-2024-45310, GHSA-jfvp-7x6p-h2pv
Record: https://patchnext.com/advisories/cve-2024-45310 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/opencontainers/runc 1.2.0-rc.3, 1.1.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/opencontainers/runc: affected < 1.1.14; >= 1.2.0-rc.1, < 1.2.0-rc.3; fixed in 1.1.14, 1.2.0-rc.3

## Suggested inspection (read-only)
- Go github.com/opencontainers/runc: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/opencontainers/runc.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jfvp-7x6p-h2pv (GitHub-reviewed advisory GHSA-jfvp-7x6p-h2pv lists affected ranges: Go github.com/opencontainers/runc >=0 =1.2.0-rc.1 <1.2.0-rc.3)

Commands are suggestions: review each one before running it.