In Kura versions <= 5.6.2, the "Command" file-upload handler at `POST /admin/denali/file/command` extracts a client-supplied ZIP archive…
- 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. The command service must be enabled; it is disabled by default since Kura 4.0.0. Affects Kura versions up to and including 5.6.2. The upload extracts into the configured command.working.directory, taken from the PasswordCommandService OSGi service property.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In Kura versions up to 5.6.2, the Command file-upload handler can be abused by an authenticated user holding the rest.command permission to write files outside the intended extraction directory through a crafted ZIP archive. The attack can be launched remotely over the network, and it is only possible when the command service is enabled, which is not the default setup.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
In Kura versions <= 5.6.2, the "Command" file-upload handler at POST /admin/denali/file/command extracts a client-supplied ZIP archive into the configured command.working.directory. The path-containment check validateFileName() compares canonical paths with String.startsWith() without appending a trailing path separator, so an entry that canonicalises to a sibling directory sharing the same string prefix (e.g. /tmpevil/x when the intended directory is /tmp) is accepted. The handler then calls parent.mkdirs() and new FileOutputStream(newFile), creating directories and writing attacker-controlled bytes outside the intended extraction root.
The command service is disabled by default since Kura 4.0.0 [1]. The issue does not apply when the command service is disabled. The caller must be authenticated with rest.command permission.
cve.now Index
- 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/10CVSS 7.0
- 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
What to do
Check whether your setup matches what the bug needs.
The command service must be enabled; it is disabled by default since Kura 4.0.0. Affects Kura versions up to and including 5.6.2. The upload extracts into the configured command.working.directory, taken from the PasswordCommandService OSGi service property.Workaround: Disable the command service, since the issue does not apply when it is disabled. Keep it disabled until a fixed release is installed.
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-111729 (In Kura versions <= 5.6.2, the "Command" file-upload handler at `POST /admin/denali/file/command` extracts a client-supplied ZIP archive…), 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-111729 (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): - The command service must be enabled; it is disabled by default since Kura 4.0.0. (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/428) - Affects Kura versions up to and including 5.6.2. (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/428) - The upload extracts into the configured command.working.directory, taken from the PasswordCommandService OSGi service property. (source: https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/958) 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-111729 is not listed as of cve.now's last read. This KEV status is for CVE-2026-111729 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/958 - https://gitlab.eclipse.org/security/cve-assignment/-/work_items/428 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-111729 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-111729.
Timeline
- CVE published
- 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.
- Link
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-111729
Is CVE-2026-111729 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?
The Command file-upload handler extracts a client-supplied ZIP archive in a way that lets an authenticated user create directories and write files outside the intended extraction directory. Sibling directories that share a string prefix with the extraction directory are accepted.Source: gitlab.eclipse.org, gitlab.eclipse.org
Which versions are affected by CVE-2026-111729?
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 listed. The issue applies only when the command service is enabled, which has been disabled by default since Kura 4.0.0. To check, confirm the Kura version and whether the command service is enabled.Source: gitlab.eclipse.org, gitlab.eclipse.org
How do I fix CVE-2026-111729?
The checked facts do not name a fixed release. The last affected version is 5.6.2, so install the fixed version named in the vendor advisory once it is available.Source: gitlab.eclipse.org, gitlab.eclipse.org
What if there's no patch?
Disable the command service, since the issue does not apply when it is disabled. Keep it disabled until a fixed release is installed.Source: gitlab.eclipse.org, gitlab.eclipse.org