Skip to main content
cve.nowby Sazabi
← Vulnerabilities
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.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

7.4HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Kura versions <= 5.6.2 Packaged Kura installation where the JVM runs as kurad with CAP_DAC_OVERRIDE Command service enabled

Published
Last modified
Reference
Last checked
20/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

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.

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

cve.now Index

20Pcve.now Index 20 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.4/10CVSS 7.4
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 27 if CISA's SSVC rates it automatable

How the score works · Rankings

What to do

  • Check whether your setup matches what the bug needs.

    Kura versions <= 5.6.2 Packaged Kura installation where the JVM runs as kurad with CAP_DAC_OVERRIDE Command service enabled

  • Workaround: 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.

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-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.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Eclipse Foundation Eclipse Kura

    From 0.7.0 · through 5.6.2

Evidence 4

Vendor advisory · 2

Establishes: Affected and fixed versions.

  1. Link
  2. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Corrections

None so far.

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

Questions about CVE-2026-97401

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

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: gitlab.eclipse.org

Which versions are affected by CVE-2026-97401?

Eclipse Kura: from 0.7.0 through 5.6.2.Source: cve.now feed data

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: gitlab.eclipse.org

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: gitlab.eclipse.org

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: gitlab.eclipse.org

Sources

CVSS details

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

Related

More vulnerabilities