CVE-2026-109797: SAP/astonish (high)

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.

Read the original 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.

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.

Read the source excerpt

“The issue affects only the legacy Incus backend.”

github.com

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional

Exploitation0/40No signal
Exposure8/25Specific setups only, reachable over the network
Reach?/20Unknown. No tracked technology or package matched
Severity7.1/10CVSS 7.1
No patch0/5No signal

What would change the score

Would score about 65 if added to CISA KEV
Would score about 60 if CISA's SSVC rates exploitation active
Would score about 22 if CISA's SSVC rates it automatable

How the score works · Rankings

What to do

Check whether your setup matches what the bug needs.
Affects the legacy Incus sandbox backend only; Kubernetes and OpenShell deployments are not affected.
Upgrade to a fixed version: v3.6.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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.

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.

Timeline

Nov 10, 2026, 1:03 AM UTCCVE published
Nov 10, 2026, 1:13 AM UTCFirst seen by cve.now
Nov 10, 2026, 7:39 PM UTCCISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
Nov 10, 2026, 7:39 PM UTCRecord last updated

Affected versions

SAP_SE SAP/astonish
fixed in v3.6.0

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

Advisory
GitHub · SAP/astonish · Advisory GHSA-93c9-96j8-4vg9

CVE record · 2

Establishes: The identifier and description.

Record
CVE List · CVE-2026-109797
Record
NVD · CVE-2026-109797

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-109797

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: cve.now feed data

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: github.com

Which versions are affected by CVE-2026-109797?

SAP/astonish: before v3.6.0.Source: cve.now feed data

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: github.com

How do I fix CVE-2026-109797?

Upgrade SAP/astonish to v3.6.0 or later, which is the listed fixed version.Source: github.com

Cross-tenant sandbox takeover in SAP/astonish