Is github.com/opencontainers/runc 0.1 vulnerable?
Go · 2 releases from 0.1.0 to 0.1.1 · latest github.com/opencontainers/runc is 1.5.3 · checked 18 Nov 2026
Yes: 25 known advisories
Yes. github.com/opencontainers/runc 0.1.1, the last 0.1 release, is affected by 25 known security advisories (4 high, 7 medium, 14 low), including CVE-2025-52881, CVE-2025-31133, CVE-2019-16884. Upgrade to 1.3.6 or later to fix all of them.
go get github.com/opencontainers/runc@v1.3.6Is 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
Advisories affecting github.com/opencontainers/runc 0.1.1
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 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 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
Can be confused to create empty files/directories on the host in github.com/opencontainers/runc
- Affected
- <1.1.14 · >=1.2.0-rc.1 <1.2.0-rc.3
- Fixed in
- 1.1.14, 1.2.0-rc.3
runc can be confused to create empty files/directories on the host
- Affected
- <1.1.14 · >=1.2.0-rc.1 <1.2.0-rc.3
- Fixed in
- 1.1.14, 1.2.0-rc.3
Mount destinations can be swapped via symlink-exchange to cause mounts outside the rootfs in github.com/opencontainers/runc
- Affected
- <1.0.0-rc95
- Fixed in
- 1.0.0-rc95
Information Exposure in RunC in github.com/opencontainers/runc
- Affected
- <1.0.0-rc3
- Fixed in
- 1.0.0-rc3
Default inheritable capabilities for linux container should be empty in github.com/opencontainers/runc
- Affected
- <1.1.2
- Fixed in
- 1.1.2
Devices resource list treated as a blacklist by default in github.com/opencontainers/runc
- Affected
- <1.0.0-rc91
- Fixed in
- 1.0.0-rc91
Rootless: /sys/fs/cgroup is writable when cgroupns isn't unshared in github.com/opencontainers/runc
- Affected
- <1.1.5
- Fixed in
- 1.1.5
AppArmor bypass with symlinked /proc in github.com/opencontainers/runc
- Affected
- <1.1.5
- Fixed in
- 1.1.5
runc AppArmor bypass with symlinked /proc
- Affected
- <1.1.5
- Fixed in
- 1.1.5
rootless: `/sys/fs/cgroup` is writable when cgroupns isn't unshared in runc
- Affected
- <1.1.5
- Fixed in
- 1.1.5
Default inheritable capabilities for linux container should be empty
- Affected
- <1.1.2
- Fixed in
- 1.1.2
Incorrect Authorization in runc
- Affected
- <1.0.0-rc8.0.20190930145003-cad42f6e0932
- Fixed in
- 1.0.0-rc8.0.20190930145003-cad42f6e0932
devices resource list treated as a blacklist by default
- Affected
- <1.0.0-rc91
- Fixed in
- 1.0.0-rc91
Information Exposure in RunC
- Affected
- <1.0.0-rc3
- Fixed in
- 1.0.0-rc3
Overflow in netlink bytemsg length field allows attacker to override netlink-based container configuration in RunC
- Affected
- <1.0.3
- Fixed in
- 1.0.3
opencontainers runc contains procfs race condition with a shared volume mount
- Affected
- <1.0.0-rc9.0.20200122160610-2fc03cc11c77
- Fixed in
- 1.0.0-rc9.0.20200122160610-2fc03cc11c77
mount destinations can be swapped via symlink-exchange to cause mounts outside the rootfs
- Affected
- <1.0.0-rc95
- Fixed in
- 1.0.0-rc95
Authorization bypass in github.com/opencontainers/runc
- Affected
- <1.0.0-rc8.0.20190930145003-cad42f6e0932
- Fixed in
- 1.0.0-rc8.0.20190930145003-cad42f6e0932
Race condition in github.com/opencontainers/runc
- Affected
- <1.0.0-rc9.0.20200122160610-2fc03cc11c77
- Fixed in
- 1.0.0-rc9.0.20200122160610-2fc03cc11c77
Every github.com/opencontainers/runc 0.1.x release
Affected: 0.1.0 to 0.1.1. Latest github.com/opencontainers/runc: 1.5.3.
| Version | Known advisories |
|---|---|
| github.com/opencontainers/runc 0.1.1 | CVE-2026-41579, CVE-2026-41579, CVE-2025-31133, CVE-2025-52881, CVE-2025-52881, CVE-2025-31133, CVE-2024-45310, CVE-2024-45310, CVE-2021-30465, CVE-2016-9962, CVE-2022-29162, GO-2022-0396, CVE-2023-25809, CVE-2023-28642, CVE-2023-28642, CVE-2023-25809, CVE-2022-29162, CVE-2019-16884, GHSA-g54h-m393-cpwq, CVE-2016-9962, CVE-2021-43784, CVE-2019-19921, CVE-2021-30465, CVE-2019-16884, CVE-2019-19921 |
| github.com/opencontainers/runc 0.1.0 | CVE-2026-41579, CVE-2026-41579, CVE-2025-31133, CVE-2025-52881, CVE-2025-52881, CVE-2025-31133, CVE-2024-45310, CVE-2024-45310, CVE-2021-30465, CVE-2016-9962, CVE-2022-29162, GO-2022-0396, CVE-2023-25809, CVE-2023-28642, CVE-2023-28642, CVE-2023-25809, CVE-2022-29162, CVE-2019-16884, GHSA-g54h-m393-cpwq, CVE-2016-9962, CVE-2021-43784, CVE-2019-19921, CVE-2021-30465, CVE-2019-16884, CVE-2019-19921 |
Which of your client projects are still on github.com/opencontainers/runc 0.1?
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.