CVE Enrichment

CVSS
8.4 HIGH
EPSS
0.81%
EPSS Percentile
56.96%
CISA KEV
Not listed

Description

runc is a CLI tool for spawning and running containers according to the OCI specification. Versions 1.0.0-rc3 through 1.2.7, 1.3.0-rc.1 through 1.3.2, and 1.4.0-rc.1 through 1.4.0-rc.2, due to insufficient checks when bind-mounting `/dev/pts/$n` to `/dev/console` inside the container, an attacker can trick runc into bind-mounting paths which would normally be made read-only or be masked onto a path that the attacker can write to. This attack is very similar in concept and application to CVE-2025-31133, except that it attacks a similar vulnerability in a different target (namely, the bind-mount of `/dev/pts/$n` to `/dev/console` as configured for all containers that allocate a console). This happens after `pivot_root(2)`, so this cannot be used to write to host files directly -- however, as with CVE-2025-31133, this can load to denial of service of the host or a container breakout by providing the attacker with a writable copy of `/proc/sysrq-trigger` or `/proc/sys/kernel/core_pattern` (respectively). This issue is fixed in versions 1.2.8, 1.3.3 and 1.4.0-rc.3.

Technical Details

CVSS Version
4.0
CNA / NVD Source
[email protected]
Published
07-Nov-2025 03:15
Last Modified
17-Jun-2026 16:36
EPSS Date
2026-11-01
CWE
CWE-61, CWE-363

CVSS Vector

CVSS:4.0 AV:L / AC:L / AT:N / PR:N / UI:P / VC:N / VI:H / VA:N / SC:H / SI:H / SA:H / E:X / CR:X / IR:X / AR:X / MAV:X / MAC:X / MAT:X / MPR:X / MUI:X / MVC:X / MVI:X / MVA:X / MSC:X / MSI:X / MSA:X / S:X / AU:X / R:X / V:X / RE:X / U:X

Affected Products / Versions

References

Last enrichment sync: 02-Nov-2026 10:10
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.

Reported Context (2)

CVE (5)

Threat Actors (2)

MITRE ATT&CK (2)

Vendors (4)

Products (8)

Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.