CVE-2016-3697: Privilege escalation in github.com/opencontainers/runc
Summary
CVE-2016-3697: Privilege escalation in github.com/opencontainers/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
Background
The package under scrutiny is github.com/opencontainers/runc, which is written in Go. It is used as a container runtime for the Open Container Initiative (OCI) specification. The package provides functionality for spawning and running containers, managing namespaces, and setting up container environments. The vulnerability in question, identified as CVE-2016-3697, involves the GetExecUser method in the libcontainer/user package. This method incorrectly interprets numeric UIDs as usernames without proper verification, potentially allowing unauthorized privilege escalation. The package is affected in versions 0.0.0 up to and including 0.1.0.
Vulnerability Detail
The vulnerability arises from the improper interpretation of numeric UIDs as usernames in the GetExecUser method. If this method is used without validating the username format, an attacker may exploit this behavior to gain unexpected privileges. This privilege escalation can lead to unauthorized access, data breaches, and potential compromise of the containerized environment.
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 apply the fix by updating the package to the recommended version.
Conclusion
The vulnerability in github.com/opencontainers/runc (CVE-2016-3697) allows for privilege escalation, potentially leading to unauthorized access and compromise of the containerized environment. To mitigate this vulnerability, it is essential to update the package to version 0.1.1 or later. No known workarounds exist, and it is recommended to apply the fix promptly. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for github.com/opencontainers/runc →
FAQ
The vulnerability allows for privilege escalation, potentially granting unauthorized access and compromising the security of the containerized environment.
You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your Gopkg.lock file for analysis.
No, only versions 0.0.0 up to and including 0.1.0 are affected. It is recommended to update to version 0.1.1 or later to mitigate the vulnerability.
While specific exploits may exist, they have not been disclosed in the vulnerability report. However, it is crucial to apply the fix promptly to prevent potential exploitation.
Continuing to use the affected package without applying the fix leaves your container runtime environment vulnerable to privilege escalation attacks. It is strongly advised to update to the recommended version.
References
Related vulnerabilities
Recent vulnerabilities recorded for github.com/opencontainers/runc.
