# CVE-2026-14784: vxcontrol PentAGI Docker API client.go sandbox

> Remote attackers can bypass sandbox restrictions in the PentAGI Docker API client, potentially escaping container isolation.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-7wx2-8pqj-q3gr

## What is CVE-2026-14784?

CVE-2026-14784 is a medium-severity vulnerability in vxcontrol PentAGI, published on 6 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in vxcontrol PentAGI up to 2.1.0. This affects an unknown function of the file backend/pkg/docker/client.go of the component Docker API. The manipulation leads to sandbox issue. The attack may be initiated remotely. The pull request to fix this issue awaits acceptance.

Weakness: CWE-265, CWE-264

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


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

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

## Is CVE-2026-14784 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14784 is a medium-severity vulnerability in vxcontrol PentAGI, published on 6 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14784 in the wild and no public exploit code.

Affected product: vxcontrol PentAGI. 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-14784/ (Markdown: https://insights.sbomify.com/CVE-2026-14784/index.md)
```

## Sources

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

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