YUXI · CVE-2026-97693 · AI agents & MCP
FIX → 0.7.1 ✓ verified
Yuxi is an AI knowledge base and agent platform. A low-privileged user who can run commands in their own Docker sandbox can reach other tenants' sandbox files, secrets and APIs, and may gain command execution in the PostgreSQL container if default credentials remain.
first public Aug 24, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Yuxi Docker Compose deployments from 0.6.0.beta1 up to but not including 0.7.1 that enable execution-capable sandboxes. Any low-privileged user who can run commands in their own sandbox can reach other tenants' sandboxes, files and secrets, the unauthenticated provisioner API, and internal services such as PostgreSQL, Neo4j and MinIO; unchanged default credentials and a superuser PostgreSQL account make it worse. Deployments with sandboxes fully disabled and internal services isolated, or with only trusted administrators as users, can skip it.
Not affected if no-untrusted-sandbox-users, sandbox-disabled, trusted-users-only, version-0.7.1-or-later
Who cares docker, minio, neo4j, postgresql, self-hosted, yuxi
Yuxi is a large-model-based intelligent knowledge base and knowledge graph agent development platform. From 0.6.0.beta1 until 0.7.1, there is insufficient isolation between execution-capable Docker sandboxes and trusted application services. A low-privileged authenticated user who can execute commands in their own sandbox can reach other tenants' sandbox APIs, access their files and secrets, execute commands in active sandboxes, and enumerate, create, or delete sandboxes through the unauthenticated provisioner without knowing administrator, database, or MinIO credentials. Sandboxes can also reach shared internal services; if shipped default service credentials remain unchanged, an attacker can use them, and if the exposed PostgreSQL account is a superuser, obtain command execution in the PostgreSQL container. These paths can disclose or modify cross-tenant data and sandbox state or cause denial of service through sandbox deletion without a container escape or kernel vulnerability. This vulnerability is fixed in 0.7.1. Existing deployments must separately rotate persisted PostgreSQL, Neo4j, or MinIO credentials that were previously set to documented or shipped defaults because upgrading the Compose files does not automatically rotate them.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to 0.7.1
Upgrade Yuxi to 0.7.1 or later, set a unique SANDBOX_PROVISIONER_TOKEN, and rotate any PostgreSQL, Neo4j or MinIO credentials still set to shipped defaults (the upgrade does not rotate credentials already stored in existing data volumes).
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.