# Moby (Docker Engine) Insufficiently restricted permissions on data directory Advisory record · `GHSA-3fwx-pjgw-3558` - **Identifiers:** `GHSA-3fwx-pjgw-3558` · `CVE-2021-41091` · `GO-2024-2500` - **State:** Confirmed - **Severity:** CVSS 6.3 Medium - **Critical:** No - **Weakness (CWE):** [CWE-281](https://cwe.mitre.org/data/definitions/281.html) · [CWE-732](https://cwe.mitre.org/data/definitions/732.html) - **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [CWE-281](https://agentprime.io/advisories/tag/cwe-281.md) - **Published:** 31 Jan 2024 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 31 Jan 2024, 23:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/moby/moby` (Go): affected `<20.10.9`; fixed in `20.10.9` - `github.com/docker/docker` (Go): affected `<20.10.9`; fixed in `20.10.9` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Moby (Docker Engine) versions before 20.10.9 have a flaw where subdirectories of the data directory (typically /var/lib/docker) have insufficiently restricted permissions. A local unprivileged Linux user can traverse these directories and run setuid programs in containers, or read and modify container files if their host UID collides with a file owner or group. Upgrade to Docker Engine 20.10.9 and restart running containers so the permissions are fixed. Until then, limit host access to trusted users and limit host volume access to trusted containers. Written 2 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 - 6.3 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.028, the 86th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:15 UTC: First seen by agentprime - 31 Oct 2026, 14:15 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3fwx-pjgw-3558) ## Sources - [GitHub Advisory Database: GHSA-3fwx-pjgw-3558](https://github.com/advisories/GHSA-3fwx-pjgw-3558) - [OSV: GHSA-3fwx-pjgw-3558](https://osv.dev/vulnerability/GHSA-3fwx-pjgw-3558) - - - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .