How severe is GHSA-g7v2-2qxx-wjrw?

No CVSS score has been assigned to GHSA-g7v2-2qxx-wjrw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g7v2-2qxx-wjrw?

GHSA-g7v2-2qxx-wjrw affects the following packages: github.com/docker/docker (Go). Ecosystems affected: Go.

How do I fix GHSA-g7v2-2qxx-wjrw?

Update github.com/docker/docker to 1.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g7v2-2qxx-wjrw is resolved across your whole dependency graph.

How do I detect GHSA-g7v2-2qxx-wjrw in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/docker/docker, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g7v2-2qxx-wjrw if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-g7v2-2qxx-wjrw actively exploited in the wild?

No public exploit code has been indexed for GHSA-g7v2-2qxx-wjrw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-g7v2-2qxx-wjrw?

GHSA-g7v2-2qxx-wjrw has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-g7v2-2qxx-wjrw?

GHSA-g7v2-2qxx-wjrw is classified as CWE-59 (CWE-59). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g7v2-2qxx-wjrw published, and has it been updated?

GHSA-g7v2-2qxx-wjrw was published on February 15, 2022 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Symlink Attack in Libcontainer and Docker EngineGHSA-g7v2-2qxx-wjrw

Fix: docker/docker@d5ebb60

GHSA-g7v2-2qxx-wjrw is a CWE-59 vulnerability in github.com/docker/docker. A fix is available for github.com/docker/docker — see the affected versions and patch details below.

Also known asCVE-2015-3627GO-2022-0649

Published

Feb 15, 2022

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/docker/docker

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Libcontainer and Docker Engine before 1.6.1 opens the file-descriptor passed to the pid-1 process before performing the chroot, which allows local users to gain privileges via a symlink attack in an image.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/docker/docker`	all versions	1.6.1`go get github.com/docker/docker@v1.6.1`

Affected Products

2 products · 2 configurations

Application

dockerdocker

≤ 1.6

range

Application

libcontainerdocker

≤ 1.6.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/docker/docker, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/docker/docker to 1.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g7v2-2qxx-wjrw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux 7 Extras	`docker-0:1.6.2-14.el7`	RHBA-2015:1167

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-g7v2-2qxx-wjrw in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works