Is there a patch available for CVE-2026-14784?

Yes, a patch is available for CVE-2026-14784. Update the affected software to the latest version immediately.

PentAGI CVE-2026-14784

Q: What is the CVSS score of CVE-2026-14784?

CVE-2026-14784 has a CVSS 4.0 base score of 5.3 (Medium). CVSS vector: 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

EUVD-2026-41795 MEDIUM

Privilege Issues (CWE-265)

2026-07-06 VulDB

GHSA-7wx2-8pqj-q3gr

Information Disclosure Docker Pentagi Vxcontrol

5.3

CVSS 4.0 · Vendor: VulDB

Severity by source

Vendor (VulDB) PRIMARY

5.3 MEDIUM

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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

6.3 MEDIUM

Network-reachable via PentAGI API requiring low-privilege authentication; sandbox breach yields limited C/I/A impact with no scope change to the underlying host.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Jul 06, 2026 - 00:42 vuln.today

DescriptionCVE.org

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.

AnalysisAI

Sandbox boundary enforcement failure in PentAGI (vxcontrol) versions up to 2.1.0 allows authenticated remote users to break Docker containment controls via the Docker API client component in backend/pkg/docker/client.go, enabling limited information disclosure and unauthorized low-impact modifications within the Docker environment. The CVSS 4.0 vector (PR:L, AV:N, AC:L) confirms low-privilege network-reachable exploitation with no user interaction required, though all impact metrics remain Low and no host-level breakout is indicated. No public exploit code exists and this vulnerability is not listed in CISA KEV; an upstream fix is pending as an unmerged GitHub pull request.

Technical ContextAI

PentAGI is an AI agent orchestration platform by vxcontrol that uses Docker to isolate and manage agent workloads. The vulnerability exists in backend/pkg/docker/client.go, the module responsible for interacting with the Docker Engine API. CWE-265 (Privilege Issues) identifies the root cause as inadequate enforcement of sandbox boundaries - the code improperly handles Docker container privilege or isolation constraints, potentially allowing a user to access Docker daemon capabilities or container resources outside their authorized scope. The CPE string cpe:2.3:a:vxcontrol:pentagi:*:*:*:*:*:*:*:* covers all versions through 2.1.0. In Docker-based agent orchestration platforms, Docker client code that mishandles privilege delegation can expose container internals, host-mounted volumes, or cross-container data to unauthorized callers.

RemediationAI

No released patched version has been independently confirmed at time of analysis. The upstream fix exists as pull request #355 at https://github.com/vxcontrol/pentagi/pull/355, which was awaiting merge acceptance at the time of disclosure - monitor this PR and the repository release page for a tagged fix version before upgrading. As an immediate compensating control, restrict network access to PentAGI's interface to trusted, authenticated internal users only, reducing the pool of principals who can reach the vulnerable Docker API path. Additionally, apply least-privilege Docker socket scoping within the PentAGI deployment: avoid granting the application broader Docker daemon access than operationally required, as tighter API surface limits the exploitable boundary even without a code fix. Track patch release status via the VulDB advisory at https://vuldb.com/cve/CVE-2026-14784.