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.
This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 7.5, requiring local system access to exploit but requires specific conditions to be met though user interaction is required requiring only low-level privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 1 product from linuxfoundation organizations running these solutions should prioritize assessment and patching.
Reported in 2025, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2025-11-06T20:15:49.240
2025-12-03T18:33:33.357
Analyzed
CVSSv3.1: 7.5 (HIGH)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | linuxfoundation | runc | < 1.2.8 | Yes |
| Application | linuxfoundation | runc | < 1.3.3 | Yes |
| Application | linuxfoundation | runc | 1.0.0 | Yes |
| Application | linuxfoundation | runc | 1.0.0 | Yes |
| Application | linuxfoundation | runc | 1.0.0 | Yes |
| Application | linuxfoundation | runc | 1.0.0 | Yes |
| Application | linuxfoundation | runc | 1.0.0 | Yes |
| Application | linuxfoundation | runc | 1.0.0 | Yes |
| Application | linuxfoundation | runc | 1.0.0 | Yes |
| Application | linuxfoundation | runc | 1.0.0 | Yes |
| Application | linuxfoundation | runc | 1.0.0 | Yes |
| Application | linuxfoundation | runc | 1.0.0 | Yes |
| Application | linuxfoundation | runc | 1.0.0 | Yes |
| Application | linuxfoundation | runc | 1.0.0 | Yes |
| Application | linuxfoundation | runc | 1.0.0 | Yes |
| Application | linuxfoundation | runc | 1.4.0 | Yes |
| Application | linuxfoundation | runc | 1.4.0 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For linuxfoundation's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.