CVE-2025-31133

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 1.2% (69th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2025-37945 (ENISA EUVD) · GHSA-9493-h29p-rfm2 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 7.8Exploit: Public PoCExposed 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/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.2%
EPSS %ILE
69th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 6, 2025

Last Modified

October 7, 2026

Advisory Details (5)

Auto-updated Oct 7, 2026
Patch available. Sources: github, github_commit.
GitHub advisoryMentions 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(24)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubunturunc (1.3.3-0ubuntu1~24.04.2) @ noble2026-10-27ubuntu
redhatcontainer-tools:rhel8-8060020260422144418.ad008a3a2026-04-27redhat
redhatrunc-4:1.2.9-1.el9_02026-04-15redhat
redhatopenshift/ose-rhel-coreos-8: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
redhatopenshift/ose-rhel-coreos-9:415.92.202512100122-02026-01-07redhat
redhatopenshift/ose-rhel-coreos-9:413.92.202511261311-02025-12-05redhat
redhatopenshift/ose-rhel-coreos-9:416.94.202511191934-02025-11-27redhat
redhatopenshift/ose-rhel-coreos-9:418.94.202511170715-02025-11-27redhat
redhatrunc-4:1.2.5-2.rhaos4.17.el82025-11-20redhat
redhatopenshift/ose-rhel-coreos-9: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
gogithub.com/opencontainers/runc @ 1.2.8 (fixes <= 1.2.7)—ghsa
gogithub.com/opencontainers/runc @ 1.3.3 (fixes >= 1.3.0-rc.1, <= 1.3.2)—ghsa
gogithub.com/opencontainers/runc @ 1.4.0-rc.3 (fixes >= 1.4.0-rc.1, <= 1.4.0-rc.2)—ghsa

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 11× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(4 references)

Public exploit code is referenced for this CVE (4 GitHub PoCs). Defenders should treat patch urgency accordingly.

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

    Learn about CVE-2025-31133

    Open source ↗
  • GitHub PoCscherepiuk/container-escape-ebpf
    Published Dec 31, 2025

    POCs and Tetragon Rules for CVE-2024-21626 and CVE-2025-31133

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

    CVE-2025-31133 PoC

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

Frequently asked(5)

What is CVE-2025-31133?
CVE-2025-31133 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2025-31133 published?
The CVE record for CVE-2025-31133 was published on November 6, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 7, 2026; the record at its source may have been updated since.
Is CVE-2025-31133 actively exploited?
CVE-2025-31133 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (69th 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.