# Portainer has a bind-mount restriction bypass via HostConfig.Mounts

Advisory record · `GHSA-7fw3-x4r2-g7wc`

- **Identifiers:** `GHSA-7fw3-x4r2-g7wc` · `CVE-2026-44850` · `GO-2026-5217`
- **State:** Confirmed
- **Severity:** CVSS 8.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 14 May 2026
- **Updated:** 25 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 May 2026, 16:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/portainer/portainer` (Go): affected `>=2.33.0, <2.33.8 || >=2.39.0, <2.39.2 || >=2.40.0, <2.41.0`; fixed in `2.33.8`, `2.39.2`, `2.41.0`

## Machine-written summary

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

> Portainer (Go module github.com/portainer/portainer) versions 2.33.0 before 2.33.8, 2.39.0 before 2.39.2, and 2.40.0 before 2.41.0 are affected. An authenticated regular user with container-create rights on an environment where bind mounts are disabled for non-administrators can bypass that restriction by specifying a bind mount through HostConfig.Mounts, which is not checked, and gain read and write access to the Docker host filesystem. Upgrade to 2.33.8, 2.39.2, 2.41.0 or later.

Written 7 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

- 8.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 15:07 UTC: First seen by agentprime
- 31 Oct 2026, 15:07 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7fw3-x4r2-g7wc)

## Sources

- [GitHub Advisory Database: GHSA-7fw3-x4r2-g7wc](https://github.com/advisories/GHSA-7fw3-x4r2-g7wc)
- [OSV: GHSA-7fw3-x4r2-g7wc](https://osv.dev/vulnerability/GHSA-7fw3-x4r2-g7wc)
- <https://github.com/portainer/portainer/security/advisories/GHSA-7fw3-x4r2-g7wc>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-44850>
- <https://github.com/portainer/portainer>
- <https://github.com/portainer/portainer/releases/tag/2.33.8>
- <https://github.com/portainer/portainer/releases/tag/2.39.2>
- <https://github.com/portainer/portainer/releases/tag/2.41.0>

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-7fw3-x4r2-g7wc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7fw3-x4r2-g7wc/>. Everything for agents: <https://agentprime.io/llms.txt>.
