GPU VulnDB

Database/AI/ML frameworks & serving

XAgent: path traversal in the workspace file endpoint reads any host file outside the Docker sandbox

CVSS 8.7CVE-2026-72713AI/ML frameworks & servingcurated

Impact

The /workspace/file handler takes a file_name form field with no path containment check, so parent-directory segments walk out of the agent workspace and read arbitrary files on the host - the advisory names application secrets, database credentials and system files, explicitly outside the Docker sandbox the agent is supposed to be confined to. Registration needs no email verification and default credentials are in play, so the attacker supplies their own account. Where XAgent is stood up on a GPU node to give an LLM agent a sandbox, this turns that sandbox into a read primitive against the node's filesystem, which is where inference API keys, registry pull secrets and often a kubeconfig or cloud credential live. Read-only, but the credentials it yields are the start of the next step.

Who can reach it

Any network user who can reach the XAgent web service: self-register an account (no email verification) or use default credentials, then POST a traversal path to /workspace/file.

What to do

Apply the upstream fix (commit 26f2b6edc75127af524f027c022b382967178e3a, PR 432) and restart the XAgent service; the record names no tagged release, so pull from source rather than waiting for a version number. In the meantime take XAgent off any network a tenant or the internet can reach, disable self-registration, change default credentials, and rotate any secret readable from the container's host mounts. No node drain or reboot involved.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.