Advisory record · GHSA-gp4j-w3vj-7299

Information Exposure in RunC

CVSS 6.4 MediumEPSS 0.0041 · 36th percentile

Published by the GitHub Advisory Database at 20 Dec 2021, 18:21 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/opencontainers/runcGo<1.0.0-rc31.0.0-rc3
Identifiers
GHSA-gp4j-w3vj-7299 · CVE-2016-9962 · GO-2022-0835
Weakness (CWE)
CWE-200
Published
20 Dec 2021
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of github.com/opencontainers/runc below 1.0.0-rc3 are affected. In these versions, processes started with 'runc exec' could be ptraced by the container's pid 1, so a main container process running as root could access file descriptors of the new processes during initialization, potentially leading to container escape or modification of runc state. Upgrade to 1.0.0-rc3 or later.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.4 Medium 3.0 CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0041, the 36th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:45 UTC First seen by agentprime
  2. 31 Oct 2026, 14:45 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.