ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2025-31133

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

Published Nov 6, 2025 · catalog updated Nov 6, 2025 · runc is a CLI

Last checked Oct 31, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-31133. EPSS is 1.24%. Act only if a listed version of runc is a CLI is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (runc is a CLI).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High7.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
1.24%
Remediation
Fix linked
Affected products
vendor opencontainers runc 1.3.0-rc.1, < 1.3.3

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions 1.2.7 and below, 1.3.0-rc.1 through 1.3.1, 1.4.0-rc.1 and 1.4.0-rc.2 files, runc would not perform sufficient verification that the source of the bind-mount (i.e., the container's /dev/null) was actually a real /dev/null inode when using the container's /dev/null to mask. This exposes two methods of attack: an arbitrary mount gadget, leading to host information disclosure, host denial of service, container escape, or a bypassing of maskedPaths. This issue is fixed in versions 1.2.8, 1.3.3 and

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor opencontainers runc 1.3.0-rc.1, < 1.3.31.3.0-rc.1, < 1.3.3

How to fix CVE-2025-31133

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-31133. EPSS is 1.24%. Act only if a listed version of runc is a CLI is installed.

Which versions are affected?

Compare what you have installed with opencontainers runc 1.3.0-rc.1, < 1.3.3 1.3.0-rc.1, < 1.3.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 1.24%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Related Odoo Git fixes

Quoted Community commit messages that cite this CVE. Presence of a commit is not proof that every edition or backport includes the fix. Enterprise proprietary diffs are never shown here. Timeline

  • Nov 5, 2025 · referenced

    Dockerfile: update runc binary to v1.3.3

    Dockerfile: update runc binary to v1.3.3 Update the version used in CI and for the static binaries. - release notes: https://github.com/opencontainers/runc/releases/tag/v1.3.3 - full diff: https://github.com/opencontainers/runc/compare/v1.3.2...v1.3.3 This release contains fixes for three high-severity security vulnerabilities in runc (CVE-2025-31133, CVE-2025-52565, and CVE-2025-52881). All three vulnerabilities ultimately allow (through different methods) for full container breakouts by bypassing runc's restrictions for writing to arbitrary /proc files.
    https://github.com/moby/moby/commit/35f6a780829fca1d3ef49ff96a0b3031462faeed

Timeline

Detection, updates, and resolution for this record.

  1. Nov 6, 2025 · EUVD

    Detected

    runc is a CLI tool for spawning and running containers according to the OCI specification. In versions 1.2.7 and below, 1.3.0-rc.1 through 1.3.1, 1.4.0-rc.1 and 1.4.0-rc.2 files, runc would not perform sufficient verification that the source of the bind-mount (i.e., the container's /dev/null) was actually a real /dev/null inode when using the container's /dev/null to mask. This exposes two methods

  2. Nov 6, 2025 · EUVD

    Updated

    runc is a CLI tool for spawning and running containers according to the OCI specification. In versions 1.2.7 and below, 1.3.0-rc.1 through 1.3.1, 1.4.0-rc.1 and 1.4.0-rc.2 files, runc would not perform sufficient verification that the source of the bind-mount (i.e., the container's /dev/null) was actually a real /dev/null inode when using the container's /dev/null to mask. This exposes two methods

Sources

  • CVE.orgVulnerability recordCVE-2025-31133

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-31133

    30-day exploitation probability 1.24%

    first.org
  • EUVDVulnerability recordEUVD-2025-37945

    runc is a CLI tool for spawning and running containers according to the OCI specification. In versions 1.2.7 and below, 1.3.0-rc.1 through 1.3.1, 1.4.0-rc.1 and 1.4.0-rc.2 files, runc would not perform sufficient verification that the source of the bind-mount (i.e., the container

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Oct 31, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 31, 2026
  • CVE.orgOct 25, 2026
  • EUVDOct 25, 2026