CVE-2015-3629

Libcontainer 1.6.0, as used in Docker Engine, allows local users to escape containerization ("mount namespace breakout") and write to arbitrary file on the host system via a symlink attack in an image when respawning a container.

Published: 2015-05-18 Last update: 2026-05-06 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2015-3629 is rated Moderate Risk (45.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.19%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2015-3629

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-12-01 0.06% 0.19% +0.13%
2 2025-05-18 0.20% 0.06% -0.14%
3 2025-03-30 — 0.20% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2015-3629

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
7.2 2.0 HIGH
AV:L/AC:L/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 3.9 10.0 [email protected]

Weakness enumeration for CVE-2015-3629

GitHub Security Advisory for CVE-2015-3629

GHSA-g44j-7vp3-68cv · Severity: high · Ecosystem: go — Arbitrary File Write in Libcontainer

OS Trackers for CVE-2015-3629

vendor priority summary link
debian not yet assigned CVE-2015-3629 not yet assigned priority: Debian including 1 source packages (docker.io), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2015-3629
redhat medium — https://access.redhat.com/security/cve/CVE-2015-3629
suse high — https://www.suse.com/security/cve/CVE-2015-3629/
ubuntu medium CVE-2015-3629 medium priority: Ubuntu including 1 source packages (docker.io), 9 status rows across 9 suites (precise, trusty, upstream, utopic, vivid, wily, xenial, yakkety, zesty): ignored 4, released 3, DNE 1, not-affected 1. https://ubuntu.com/security/CVE-2015-3629

Affected software / configurations for CVE-2015-3629

Vendor Product Version Raw CPE
docker libcontainer 1.6.0 cpe:2.3:a:docker:libcontainer:1.6.0:*:*:*:*:docker:*:*
opensuse opensuse 13.2 cpe:2.3:o:opensuse:opensuse:13.2:*:*:*:*:*:*:*

References for CVE-2015-3629

cvelogic Threat Intelligence