CVE-2026-97693

waiting for further signalsZero needs more public information before it can validate it.

GHSA-qpm5-6332-9445 ↗EUVD-2026-117122 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
xerrors Yuxi >= 0.6.0.beta1, < 0.7.1
fixed in 0.7.1
CWE-77 Improper Neutralization of Special Elements used in a Command ('Command Injection')
ETK-2026-3545Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 59msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h30m
+2h
+4h
+6h
+8h
+10h
+12h

description

Yuxi versions from 0.6.0.beta1 before 0.7.1 inadequately isolate Docker sandboxes from other tenants and trusted internal services. An authenticated low-privilege user who can run commands in an assigned sandbox may access other tenants' data or alter sandbox state; unchanged default service credentials can increase exposure.

mitigation

Upgrade Yuxi to 0.7.1. Rotate persisted PostgreSQL, Neo4j, and MinIO credentials where documented or shipped defaults were previously used.

fixed in 0.7.1

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-04 21:14Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-04 21:14Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-97693

{
  "etk_id": "ETK-2026-3545",
  "cve_id": "CVE-2026-97693",
  "display_id": "CVE-2026-97693",
  "ghsa_id": "GHSA-qpm5-6332-9445",
  "euvd_id": "EUVD-2026-117122",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-tenant sandbox isolation flaw in Yuxi",
  "summary": "Yuxi versions from 0.6.0.beta1 before 0.7.1 inadequately isolate Docker sandboxes from other tenants and trusted internal services. An authenticated low-privilege user who can run commands in an assigned sandbox may access other tenants' data or alter sandbox state; unchanged default service credentials can increase exposure.",
  "mitigation": "Upgrade Yuxi to 0.7.1. Rotate persisted PostgreSQL, Neo4j, and MinIO credentials where documented or shipped defaults were previously used.",
  "vendor": "xerrors",
  "product": "Yuxi",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.6.0.beta1, < 0.7.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.7.1"
      ],
      "package_name": null,
      "purl": null
    }
  ],
  "cwes": [
    77
  ],
  "cvss_score": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.324666816666667,
  "t0_at": "2026-11-04T21:14:50.408000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-04T21:14:50.408000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T21:14:50.408000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-97693"
    }
  }
}

published 2026-11-04 21:34Z
last change 2026-11-05 00:05Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.