CVE-2016-9962

What it is

RunC allowed additional container processes via 'runc exec' to be ptraced by the pid 1 of the container. This allows the main processes of the container, if running as root, to gain access to file-descriptors of these new processes during the initialization and can lead to container escapes or modification of runC state before the process is fully placed inside the container.

At a glance

Exploitability

Can be exploited locally on the machine with an admin-level account. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2017-01-31 22:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:56 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 6.4 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2017-01-31 22:59 UTC

Last modified

2026-06-17 00:56 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-362 · Race condition

Record status

Modified

Affected

• Docker < 1.12.6

Attack profile CVSS 3.0 · 6.4

Attack vector

Local

Complexity

High

Privileges needed

High

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2016-9962.md and follow it. Check whether this project is affected by CVE-2016-9962. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge