# CVE-2026-77179: Docker Sandboxes guest can write arbitrary macOS host files via a symlink in the virtio-fs stored-path fallback

> A malicious guest in Docker Sandboxes on macOS can escape the shared workspace via symlink manipulation to read or modify arbitrary host files and potentially execute code.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-4x2g-7mfh-8rx6

## What is CVE-2026-77179?

CVE-2026-77179 is a critical path traversal vulnerability in Docker Sandboxes, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On macOS, the virtio-fs host server used by Docker Sandboxes improperly follows symlinks when reopening an unlinked file from a stored path. A malicious guest can replace a parent directory with a symlink, escape the shared workspace, and read or modify arbitrary host files as the VMM user, potentially achieving host code execution.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-77179?


## How do I fix CVE-2026-77179?

No fix has been published for CVE-2026-77179 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-77179 being exploited?

There is no known exploitation of CVE-2026-77179 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-77179 - Draft or TODO (github_poc): https://github.com/HORKimhab/CVE-2026-77179

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77179 and fix it if it is affected.

What it is: CVE-2026-77179 is a critical path traversal vulnerability in Docker Sandboxes, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77179 in the wild and no public exploit code.

Affected product: Docker Sandboxes. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77179/ (Markdown: https://insights.sbomify.com/CVE-2026-77179/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77179
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77179
- OSV: https://osv.dev/vulnerability/CVE-2026-77179

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77179/
Summaries are generated and may contain mistakes; the official description above is the record.