Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.9

CVE-2026-97693: Yuxi lets one user access other tenants' data

CVE-2026-97693 · published 17 days ago
Summary

Versions of Yuxi from 0.6.0.beta1 through 0.7.1 do not keep each user’s sandbox separate from the others. A low‑privilege user who can run commands in their own sandbox could read files, secrets, and APIs belonging to other customers, and could even delete or create sandboxes. Upgrade to version 0.7.1 and change any default database, Neo4j or MinIO passwords that were left unchanged.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
xerrors yuxi >= 0.6.0.beta1, < 0.7.1
Original advisory text
Yuxi sandbox isolation failure allows cross-tenant access and internal service compromise
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.
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker full control
Severity
9.9 Critical
Exploitation
1% chance of attack within 30 days
Type
CWE-77Command Injection
CWE-284Improper Access Control
CWE-522Insufficiently Protected Credentials
Timeline
Published4 Nov 2026
Updated22 Nov 2026
First seen4 Nov 2026
Sources
CVE-2026-97693 · MITRE
Track software like this
Free during beta