CVE-2025-31133

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.8% (56th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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 1.4.0-rc.3.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
51
EG Risk 51/100CISA SSVC

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
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

November 6, 2025

Last Modified

October 7, 2026

Advisory Details (5)

Auto-updated Oct 7, 2026
Patch available. Sources: github, github_commit.
githubMentions a patch (unverified)

container escape via "masked path" abuse due to mount race conditions · Advisory · opencontainers/runc · GitHub

https://github.com/opencontainers/runc/security/advisories/GHSA-9493-h29p-rfm2
github_commit

commit db19bbed5348 (opencontainers/runc)

Fix landed in opencontainers/runc commit db19bbed5348 — awaiting tagged release

https://github.com/opencontainers/runc/commit/db19bbed5348847da433faa9d69e9f90192bfa64
github_commit

commit 8476df83b534 (opencontainers/runc)

Fix landed in opencontainers/runc commit 8476df83b534 — awaiting tagged release

https://github.com/opencontainers/runc/commit/8476df83b534a2522b878c0507b3491def48db9f
github_commit

commit 5d7b24240724 (opencontainers/runc)

Fix landed in opencontainers/runc commit 5d7b24240724 — awaiting tagged release

https://github.com/opencontainers/runc/commit/5d7b2424072449872d1cd0c937f2ca25f418eb66
github_commit

commit 1a30a8f3d921 (opencontainers/runc)

Fix landed in opencontainers/runc commit 1a30a8f3d921 — awaiting tagged release

https://github.com/opencontainers/runc/commit/1a30a8f3d921acbbb6a4bb7e99da2c05f8d48522

Patch Availability(21)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubunturunc-stable (1.3.3-0ubuntu1~25.10.2) @ questing2026-05-29ubuntu
redhatcontainer-tools:rhel8-8060020260422144418.ad008a3a2026-04-27redhat
redhatrunc-4:1.2.9-1.el9_02026-04-15redhat
redhatrhcos-412.86.202604010116-02026-04-09redhat
redhatcontainer-tools:rhel8-8080020260226135022.63b345852026-03-17redhat
redhatrunc-4:1.2.9-1.el9_2.12026-03-12redhat
redhatquay/quay-builder-rhel9:17708164382026-02-12redhat
redhatrunc-4:1.2.9-1.rhaos4.16.el82026-02-05redhat
redhatrunc-4:1.2.9-1.rhaos4.17.el92026-01-22redhat
redhatrunc-4:1.2.9-1.rhaos4.17.el82026-01-15redhat
redhatrunc-4:1.2.9-1.rhaos4.18.el82026-01-15redhat
redhatrunc-4:1.2.9-1.el9_42026-01-12redhat
redhatrhcos-415.92.202512100122-02026-01-07redhat
redhatrhcos-413.92.202511261311-02025-12-05redhat
redhatrhcos-416.94.202511191934-02025-11-27redhat
redhatrhcos-418.94.202511170715-02025-11-27redhat
redhatrunc-4:1.2.5-2.rhaos4.17.el82025-11-20redhat
redhatrhcos-4.20.9.6.202511102206-02025-11-18redhat
redhatcontainer-tools:rhel8-8100020251112161627.afee755d2025-11-13redhat
redhatrunc-4:1.3.0-4.el9_72025-11-11redhat
redhatrunc-4:1.2.5-3.el9_62025-11-07redhat

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.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
runc1.0.0+ds1-1 ... 1.3.5+ds1-1 (50 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
runc1.1.10+ds1-1 ... 1.4.3+ds1-1 (26 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
runc1.1.15+ds1-2 ... 1.4.3+ds1-1 (12 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
runc1.1.15+ds1-2 ... 1.3.3+ds1-1 (7 versions)
  • every version up to 1.3.3+ds1-2: fixed in 1.3.3+ds1-2
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/opencontainers/runc—
  • every version up to 1.2.8: fixed in 1.2.8
  • 1.3.0-rc.1 up to 1.3.3: fixed in 1.3.3
  • 1.4.0-rc.1 up to 1.4.0-rc.3: fixed in 1.4.0-rc.3
—

Weakness Classification(2)

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

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 9× in last 7d / 29× 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.

Showing the most recent 100 of 167 total refreshes for this CVE.

  1. 2026-10-09 20:06 UTCEPSS rescore
  2. 2026-10-08 17:09 UTCEPSS rescore
  3. 2026-10-07 23:46 UTCEPSS rescore
  4. 2026-10-07 21:40 UTCEG score recompute
  5. 2026-10-07 21:40 UTCVendor advisory
  6. 2026-10-06 15:16 UTCEPSS rescore
  7. 2026-10-05 17:42 UTCEPSS rescore
  8. 2026-10-04 23:21 UTCEPSS rescore
  9. 2026-10-03 14:24 UTCEPSS rescore
  10. 2026-10-02 01:11 UTCOSV refresh
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-09-30 15:02 UTCEPSS rescore
  13. 2026-09-29 15:19 UTCEPSS rescore
  14. 2026-09-28 13:50 UTCEPSS rescore
  15. 2026-09-26 15:58 UTCEPSS rescore
  16. 2026-09-26 15:58 UTCEPSS rescore
  17. 2026-09-26 00:24 UTCEPSS rescore
  18. 2026-09-26 00:24 UTCEPSS rescore
  19. 2026-09-24 14:02 UTCEPSS rescore
  20. 2026-09-23 13:47 UTCEPSS rescore
  21. 2026-09-18 19:27 UTCEPSS rescore
  22. 2026-09-16 14:07 UTCEPSS rescore
  23. 2026-09-16 05:13 UTCEPSS rescore
  24. 2026-09-13 16:46 UTCEPSS rescore
  25. 2026-09-12 18:36 UTCOSV refresh
Show 75 more
  1. 2026-09-12 15:00 UTCEPSS rescore
  2. 2026-09-11 14:52 UTCEPSS rescore
  3. 2026-09-11 09:35 UTCEPSS rescore
  4. 2026-09-10 09:33 UTCEPSS rescore
  5. 2026-09-08 21:59 UTCEPSS rescore
  6. 2026-09-07 16:00 UTCEPSS rescore
  7. 2026-09-06 13:46 UTCEPSS rescore
  8. 2026-09-06 13:46 UTCEPSS rescore
  9. 2026-09-04 05:05 UTCEPSS rescore
  10. 2026-09-02 14:11 UTCEPSS rescore
  11. 2026-09-01 13:53 UTCEPSS rescore
  12. 2026-08-30 19:16 UTCEPSS rescore
  13. 2026-08-30 19:16 UTCEPSS rescore
  14. 2026-08-30 01:21 UTCEPSS rescore
  15. 2026-08-28 21:40 UTCEPSS rescore
  16. 2026-08-27 14:24 UTCEPSS rescore
  17. 2026-08-26 14:45 UTCEPSS rescore
  18. 2026-08-25 13:48 UTCEPSS rescore
  19. 2026-08-24 23:44 UTCOSV refresh
  20. 2026-08-24 14:16 UTCEPSS rescore
  21. 2026-08-23 00:18 UTCEPSS rescore
  22. 2026-08-21 23:48 UTCEPSS rescore
  23. 2026-08-19 17:03 UTCEPSS rescore
  24. 2026-08-18 13:47 UTCEPSS rescore
  25. 2026-08-17 13:46 UTCEPSS rescore
  26. 2026-08-16 14:55 UTCEPSS rescore
  27. 2026-08-16 02:13 UTCEPSS rescore
  28. 2026-08-15 01:29 UTCEPSS rescore
  29. 2026-08-13 21:59 UTCEPSS rescore
  30. 2026-08-12 13:50 UTCEPSS rescore
  31. 2026-08-10 23:59 UTCEPSS rescore
  32. 2026-08-09 13:45 UTCEPSS rescore
  33. 2026-08-08 17:19 UTCOSV refresh
  34. 2026-08-07 16:26 UTCEPSS rescore
  35. 2026-08-06 13:46 UTCEPSS rescore
  36. 2026-08-05 19:16 UTCEPSS rescore
  37. 2026-08-04 15:09 UTCEPSS rescore
  38. 2026-08-04 10:37 UTCEPSS rescore
  39. 2026-08-03 10:35 UTCEPSS rescore
  40. 2026-08-02 02:26 UTCEPSS rescore
  41. 2026-08-01 04:15 UTCEPSS rescore
  42. 2026-07-30 16:27 UTCEPSS rescore
  43. 2026-07-30 01:29 UTCEPSS rescore
  44. 2026-07-28 15:35 UTCEPSS rescore
  45. 2026-07-27 14:12 UTCEPSS rescore
  46. 2026-07-26 14:53 UTCEPSS rescore
  47. 2026-07-25 14:17 UTCEPSS rescore
  48. 2026-07-24 14:17 UTCEPSS rescore
  49. 2026-07-23 16:11 UTCOSV refresh
  50. 2026-07-23 02:53 UTCEG score recompute
  51. 2026-07-22 14:07 UTCEPSS rescore
  52. 2026-07-22 14:07 UTCEPSS rescore
  53. 2026-07-21 15:24 UTCEPSS rescore
  54. 2026-07-21 15:24 UTCEPSS rescore
  55. 2026-07-20 17:07 UTCEPSS rescore
  56. 2026-07-19 14:30 UTCEPSS rescore
  57. 2026-07-19 14:30 UTCEPSS rescore
  58. 2026-07-19 02:28 UTCEPSS rescore
  59. 2026-07-19 02:28 UTCEPSS rescore
  60. 2026-07-18 10:04 UTCEPSS rescore
  61. 2026-07-18 10:04 UTCEPSS rescore
  62. 2026-07-16 17:02 UTCEPSS rescore
  63. 2026-07-15 16:57 UTCEPSS rescore
  64. 2026-07-15 16:57 UTCEPSS rescore
  65. 2026-07-15 01:59 UTCEPSS rescore
  66. 2026-07-15 01:59 UTCEPSS rescore
  67. 2026-07-13 22:29 UTCEPSS rescore
  68. 2026-07-13 06:12 UTCEPSS rescore
  69. 2026-07-13 06:12 UTCEPSS rescore
  70. 2026-07-12 05:46 UTCEPSS rescore
  71. 2026-07-12 05:46 UTCEPSS rescore
  72. 2026-07-11 08:27 UTCEPSS rescore
  73. 2026-07-11 08:27 UTCEPSS rescore
  74. 2026-07-09 19:09 UTCEPSS rescore
  75. 2026-07-08 15:14 UTCEPSS rescore

Publicly available exploits

(3 references)

Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCC-h4ck-0/Learn-about-cve-2025-31133-poc
    First seen Jan 18, 2026

    Learn about CVE-2025-31133

    Open source ↗
  • GitHub PoCskynet-f-nvidia/CVE-2025-31133
    First seen Nov 12, 2025

    CVE-2025-31133 PoC

    Open source ↗
  • GitHub PoCsahar042/CVE-2025-31133
    First seen Nov 6, 2025
    Open source ↗

Frequently asked(5)

What is CVE-2025-31133?
CVE-2025-31133 is a high vulnerability published on November 6, 2025. 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…
When was CVE-2025-31133 disclosed?
CVE-2025-31133 was first published on November 6, 2025, with the most recent update on October 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-31133 actively exploited?
CVE-2025-31133 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-31133?
CVE-2025-31133 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-31133?
A fix for CVE-2025-31133 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-31133 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-31133

Explore →

Is Your Infrastructure Affected by CVE-2025-31133?

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