# Symlink Attack in Libcontainer and Docker Engine

Advisory record · `GHSA-g7v2-2qxx-wjrw`

- **Identifiers:** `GHSA-g7v2-2qxx-wjrw` · `CVE-2015-3627` · `GO-2022-0649`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-59](https://cwe.mitre.org/data/definitions/59.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 15 Feb 2022
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 15 Feb 2022, 01:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/docker/docker` (Go): affected `<1.6.1`; fixed in `1.6.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Docker Engine (github.com/docker/docker) versions before 1.6.1, and libcontainer, are vulnerable. A local user who can supply a crafted image can use a symlink attack, because the file descriptor passed to the pid-1 process is opened before the chroot is performed, which may allow privilege escalation. Upgrade to Docker Engine 1.6.1 or later.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0061, the 50th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:45 UTC: First seen by agentprime
- 31 Oct 2026, 14:45 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-g7v2-2qxx-wjrw)

## Sources

- [GitHub Advisory Database: GHSA-g7v2-2qxx-wjrw](https://github.com/advisories/GHSA-g7v2-2qxx-wjrw)
- [OSV: GHSA-g7v2-2qxx-wjrw](https://osv.dev/vulnerability/GHSA-g7v2-2qxx-wjrw)
- <https://nvd.nist.gov/vuln/detail/CVE-2015-3627>
- <https://github.com/docker/docker/commit/d5ebb60bddbabea0439213501f4f6ed494b23cba>
- <https://groups.google.com/forum/#!searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ>
- <https://groups.google.com/forum/#%21searchin/docker-user/1.6.1/docker-user/47GZrihtr-4/nwgeOOFLexIJ>
- <https://lists.opensuse.org/opensuse-updates/2015-05/msg00023.html>
- <https://packetstormsecurity.com/files/131835/Docker-Privilege-Escalation-Information-Disclosure.html>
- <https://seclists.org/fulldisclosure/2015/May/28>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-g7v2-2qxx-wjrw>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-g7v2-2qxx-wjrw/>. Everything for agents: <https://agentprime.io/llms.txt>.
