CVE-2016-3697: Privilege Elevation in runc
Summary
CVE-2016-3697: Privilege Elevation in runc. Affects github.com/opencontainers/runc versions < 0.1.0. Fixed in 0.1.0. How to fix ↓
Also tracked for
- runc · Debian:11
The same CVE-2016-3697 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package under scrutiny is github.com/opencontainers/runc, which is written in Go. It is a lightweight, portable container runtime that provides an interface for creating and managing containers. Runc is widely used in containerization platforms, including Docker. This vulnerability affects versions prior to 0.1.0 of runc and Docker versions prior to 1.11.2. The vulnerability allows local users to gain privileges by exploiting the improper treatment of a numeric UID as a potential username in the password file within a container.
Vulnerability Detail
The vulnerability (CVE-2016-3697) in runc arises from the incorrect handling of a numeric UID as a potential username. This flaw enables local users to elevate their privileges within a container by using a numeric username in the password file. By exploiting this vulnerability, an attacker with access to a container can gain elevated privileges, potentially leading to unauthorized access, data breaches, or further compromise of the host system. The severity of this vulnerability is rated as HIGH with a CVSS score of 7.8.
How To Fix
Latest published version: v1.5.2 as of 22 Oct 2026
go get github.com/opencontainers/runc@v1.5.2Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
0.1.0
This is the first release that contains the fix.
go get github.com/opencontainers/runc@v0.1.0Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is crucial to update the affected packages to the patched versions as mentioned in the 'how_to_fix' section.
Conclusion
The vulnerability (CVE-2016-3697) in runc allows local users to gain privileges within a container by exploiting the improper treatment of a numeric UID as a potential username. To mitigate this vulnerability, it is crucial to update runc to version 0.1.0 or later, and Docker to version 1.11.2 or later. No workarounds are available, and it is recommended to update the affected packages promptly. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for github.com/opencontainers/runc →
FAQ
This vulnerability allows local users within a container to gain elevated privileges, potentially leading to unauthorized access, data breaches, or further compromise of the host system.
Versions of runc prior to 0.1.0 and Docker versions prior to 1.11.2 are affected by this vulnerability.
No, there are no known workarounds for this vulnerability. Updating the affected packages is the recommended solution.
This vulnerability is rated as HIGH with a CVSS score of 7.8.
You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.
References
Related vulnerabilities
Recent vulnerabilities recorded for github.com/opencontainers/runc.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
