Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with rest.command permission
-
DeliverySend crafted ZIP to CommandCloudApp.execute
-
ExploitSet workingDirectory to '/'
-
ExecutionArchive extracted as kurad (CAP_DAC_OVERRIDE)
-
ImpactOverwrite arbitrary files, escape unprivileged sandbox
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File name/path control
|
| Exploitation Conditions | Exploitation requires ALL of: (1) the Kura command service is enabled - it is disabled by default since Kura 4.0.0, and the issue does not apply when it is disabled; (2) a packaged Kura installation where the JVM runs as |
| Impact | This is a genuine but conditional privilege/sandbox-escape issue rather than a mass-exploitation threat. The Eclipse-assigned CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:L/UI:N) describes a network-reachable flaw requiring low privileges - specifically a caller already holding the |
| Exploit ScenarioDerived | An operator enables the Kura command service but intentionally restricts a REST caller to unprivileged execution ( |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 10, 2026
Arbitrary file write as the kurad JVM user in Eclipse Kura through 5.6.2 lets an authenticated caller with rest.command bypass the operator-selected unprivileged command sandbox by setting workingDirectory to / and supplying a ZIP body to CommandCloudApp.execute(). This is a conditional sandbox-escape rather than a mass-exploitation threat: the command service must be enabled (disabled by default since Kura 4.0.0, and the issue does not apply when disabled), the installation must run the JVM as kurad with CAP_DAC_OVERRIDE, and the Unprivileged executor must be selected. It is rated 7.4 with priority this_week; no public exploit identified at time of analysis, and no CISA KEV entry is present.
RemediationAI
No fixed Kura release is listed in the supplied data, so a specific patched version cannot be confirmed; check the Eclipse security work item at https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/922 for the vendor's fixed-release guidance. The mitigation confirmed by the advisory is to keep the command service disabled; it is disabled by default since Kura 4.0.0, and the issue does not apply when it is disabled. If the service must remain enabled, restrict the rest.command permission to trusted callers because exploitation requires that permission, and do not rely on the Unprivileged executor (privileged.command.service.enable=false) to sandbox file writes in packaged installations where the JVM runs as kurad with CAP_DAC_OVERRIDE.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Eclipse Kura is a Java-based IoT gateway runtime, and CommandCloudApp is its REST-facing command service. The root cause is CWE-73 (external control of file name/path): CommandCloudApp.execute() accepts a caller-supplied workingDirectory and a caller-supplied ZIP archive and extracts the archive inside the Kura JVM process before dispatching the command to the executor service. On packaged installations the JVM runs as kurad with CAP_DAC_OVERRIDE, while the configurable Unprivileged executor later drops to the kura user via su; because extraction precedes that privilege drop, an unprivileged-mode caller can write or overwrite files as kurad by choosing / as the working directory. The supplied sources confirm the controllable extraction location and the pre-drop timing as the mechanism but do not describe the exact archive path handling. The vulnerability is limited to deployments where the command service is enabled; it is disabled by default since Kura 4.0.0.
Know when Eclipse Kura gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Network REST access with existing rest.command rights gives AV:N/PR:L; arbitrary file write as kurad escapes the executor boundary (S:C) with high integrity/availability and limited confidentiality impact.
Primary rating from Vendor (eclipse).
CVSS VectorVendor: eclipse
DescriptionCVE.org
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
Executive ViewAI
A high-severity vulnerability in Eclipse Kura (up to 5.6.2) allows an authenticated user with rest.command privileges to bypass the unprivileged command sandbox and write arbitrary files as the kurad JVM user. Exploitation requires the command service to be enabled (disabled by default since Kura 4.0.0), the JVM to run as kurad with CAP_DAC_OVERRIDE, and the Unprivileged executor selected. While no public exploit exists and mass exploitation is unlikely, organizations using Kura for IoT/edge deployments should verify their configuration and apply mitigations to prevent potential unauthorized file writes.
Disable the command service (if not required), restrict rest.command access, avoid running the JVM as kurad with CAP_DAC_OVERRIDE, and consider switching from the Unprivileged executor to a more restrictive alternative. Monitor file system activity for anomalous writes.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Eclipse Kura
View allLog integrity spoofing in Eclipse Kura before 5.6.2 lets an unauthenticated remote attacker forge the client IP recorded
Unbounded HTTP session allocation in the Eclipse Kura Web Console (versions 5.0.0 through 5.6.2) lets an unauthenticated
Unauthenticated denial of service in Eclipse Kura 5.4.0 through 5.6.2 lets a remote client exhaust the gateway's Java he
Improper authorization in Eclipse Kura 5.1.0 through 5.6.2 lets an authenticated identity that holds only the rest.confi
Authenticated Eclipse Kura identities that hold the rest.identity permission but lack kura.admin can use the Identity RE
Eclipse Kura 5.0.0 through 5.6.2 allows an authenticated user who holds only the Wires management permission (kura.wires
Authenticated path traversal in Eclipse Kura 5.6.2 and earlier lets a user holding the `rest.command` permission write a
Denial of service in Eclipse Kura is a moderate-priority, availability-only issue: an authenticated user who can install
EUVD-2026-121411
NVD
CVE.org
GitHub PoC
Exploit-DB