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.
Severity
CVSS 3.1
9.9 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CWEs
CWE-77Improper Neutralization of Special Elements used in a Command CWE-284Improper Access Control CWE-522Insufficiently Protected Credentials
Show the promptExplain CVE-2026-97693 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97693?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97693?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-97693 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Versions
From the CNA's record in the CVE List.
Product
Affected
xerrors Yuxi
>= 0.6.0.beta1, < 0.7.1
Attack patterns (CAPEC)
CAPEC-15 Command Delimiters Likelihood: High · Severity: High
CAPEC-40 Manipulating Writeable Terminal Devices Likelihood: High · Severity: Very High
CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
CAPEC-136 LDAP Injection Likelihood: High · Severity: High
CAPEC-183 IMAP/SMTP Command Injection Severity: Medium
CAPEC-248 Command Injection Likelihood: Medium · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-522 (13), CWE-284 (17).