# opencontainers runc contains procfs race condition with a shared volume mount Advisory record · `GHSA-fh74-hm69-rqjw` - **Identifiers:** `GHSA-fh74-hm69-rqjw` · `CVE-2019-19921` · `GO-2021-0087` - **State:** Confirmed - **Severity:** CVSS 5.9 Medium - **Critical:** No - **Weakness (CWE):** [CWE-362](https://cwe.mitre.org/data/definitions/362.html) · [CWE-706](https://cwe.mitre.org/data/definitions/706.html) - **Tags:** [Race condition](https://agentprime.io/advisories/tag/race-condition.md) · [CWE-706](https://agentprime.io/advisories/tag/cwe-706.md) - **Published:** 27 May 2021 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 27 May 2021, 18:41 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/opencontainers/runc` (Go): affected `<1.0.0-rc9.0.20200122160610-2fc03cc11c77`; fixed in `1.0.0-rc9.0.20200122160610-2fc03cc11c77` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The Go package github.com/opencontainers/runc is vulnerable before version 1.0.0-rc9.0.20200122160610-2fc03cc11c77, and the fixed version is the same as that value. An attacker who controls a malicious root filesystem and can create containers with custom mounts sharing a volume with another running container could cause runc to misconfigure security labels and fail to mask sensitive /proc paths. Upgrade runc to the fixed version; the advisory notes the fix is a hot-fix with known workarounds, so review which users can configure container mounts. 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 - 5.9 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:U/RC:U`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.0043, the 37th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:44 UTC: First seen by agentprime - 31 Oct 2026, 14:44 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-fh74-hm69-rqjw) ## Sources - [GitHub Advisory Database: GHSA-fh74-hm69-rqjw](https://github.com/advisories/GHSA-fh74-hm69-rqjw) - [OSV: GHSA-fh74-hm69-rqjw](https://osv.dev/vulnerability/GHSA-fh74-hm69-rqjw) - - - - - - - - - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .