Is github.com/opencontainers/runc 1.3 vulnerable?
Go · 8 releases from 1.3.0 to 1.3.7 · latest github.com/opencontainers/runc is 1.5.3 · checked 18 Nov 2026
No known advisories in the last release
github.com/opencontainers/runc 1.3.7, the last 1.3 release, has no known advisories. 8 advisories affect earlier 1.3.x releases, so update to 1.3.7.
go get github.com/opencontainers/runc@v1.3.7Is your project on an affected github.com/opencontainers/runc?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 1.3.x, affecting earlier releases
Malicious image with /dev symlink can trigger limited host filesystem integrity violations in github.com/opencontainers/runc
- Affected
- <1.3.6 · >=1.4.0 <1.4.3 · >=1.5.0-rc.1 <1.5.0-rc.3
- Fixed in
- 1.3.6, 1.4.3, 1.5.0-rc.3
runc: Malicious image with /dev symlink can trigger limited host filesystem integrity violations
- Affected
- <1.3.6 · >=1.4.0 <1.4.3 · >=1.5.0-rc.1 <1.5.0-rc.3
- Fixed in
- 1.3.6, 1.4.3, 1.5.0-rc.3
Container escape via "masked path" abuse due to mount race conditions in github.com/opencontainers/runc
- Affected
- <1.2.8 · >=1.3.0-rc.1 <1.3.3 · >=1.4.0-rc.1 <1.4.0-rc.3
- Fixed in
- 1.2.8, 1.3.3, 1.4.0-rc.3
Container escape with malicious config due to /dev/console mount and related races in github.com/opencontainers/runc
- Affected
- >=1.0.0-rc3 <1.2.8 · >=1.3.0-rc.1 <1.3.3 · >=1.4.0-rc.1 <1.4.0-rc.3
- Fixed in
- 1.2.8, 1.3.3, 1.4.0-rc.3
Container escape and DDoS due to arbitrary write gadgets and procfs write redirects in github.com/opencontainers/runc
- Affected
- <1.2.8 · >=1.3.0-rc.1 <1.3.3 · >=1.4.0-rc.1 <1.4.0-rc.3
- Fixed in
- 1.2.8, 1.3.3, 1.4.0-rc.3
runc container escape and denial of service due to arbitrary write gadgets and procfs write redirects
- Affected
- <1.2.8 · >=1.3.0-rc.1 <1.3.3 · >=1.4.0-rc.1 <1.4.0-rc.3
- Fixed in
- 1.2.8, 1.3.3, 1.4.0-rc.3
runc container escape with malicious config due to /dev/console mount and related races
- Affected
- >=1.0.0-rc3 <1.2.8 · >=1.3.0-rc.1 <1.3.3 · >=1.4.0-rc.1 <1.4.0-rc.3
- Fixed in
- 1.2.8, 1.3.3, 1.4.0-rc.3
runc container escape via "masked path" abuse due to mount race conditions
- Affected
- <1.2.8 · >=1.3.0-rc.1 <1.3.3 · >=1.4.0-rc.1 <1.4.0-rc.3
- Fixed in
- 1.2.8, 1.3.3, 1.4.0-rc.3
Every github.com/opencontainers/runc 1.3.x release
Affected: 1.3.0 to 1.3.5. 1.3.6 and later are not affected. Latest github.com/opencontainers/runc: 1.5.3.
| Version | Known advisories |
|---|---|
| github.com/opencontainers/runc 1.3.7 | None |
| github.com/opencontainers/runc 1.3.6 | None |
| github.com/opencontainers/runc 1.3.5 | CVE-2026-41579, CVE-2026-41579 |
| github.com/opencontainers/runc 1.3.4 | CVE-2026-41579, CVE-2026-41579 |
| github.com/opencontainers/runc 1.3.3 | CVE-2026-41579, CVE-2026-41579 |
| github.com/opencontainers/runc 1.3.2 | CVE-2026-41579, CVE-2026-41579, CVE-2025-31133, CVE-2025-52565, CVE-2025-52881, CVE-2025-52881, CVE-2025-52565, CVE-2025-31133 |
| github.com/opencontainers/runc 1.3.1 | CVE-2026-41579, CVE-2026-41579, CVE-2025-31133, CVE-2025-52565, CVE-2025-52881, CVE-2025-52881, CVE-2025-52565, CVE-2025-31133 |
| github.com/opencontainers/runc 1.3.0 | CVE-2026-41579, CVE-2026-41579, CVE-2025-31133, CVE-2025-52565, CVE-2025-52881, CVE-2025-52881, CVE-2025-52565, CVE-2025-31133 |
Which of your client projects are still on github.com/opencontainers/runc 1.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/opencontainers/runc version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/opencontainers/runc versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.