Read the docs

Missing size limit in Eclipse Kura deployment package downloads

Priority LOW 30CWE-770Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · High
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-770.

Summary

Eclipse Kura from 0.7.0 through 5.6.2 downloads deployment packages from a remote URL without limiting the size of the received data (CWE-770). A malicious or compromised HTTP(S) server, or an attacker who can tamper with plain-HTTP downloads, can stream an endless response that fills local storage or RAM-backed temporary space. The result is denial of service, with failed logging, failed configuration persistence and possible crashes. The REST upload endpoint POST /deploy/v2/_upload has the same missing limit.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

Description from the CNA

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

Why it matters now

EPSS 0.00235 14th percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
Eclipse FoundationEclipse Kura0.7.0 – 5.6.2—No fix listedCNA
  • Eclipse Kura VendorEclipse Foundation Affected 0.7.0 – 5.6.2 Fixed in — No fix listed CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:eclipse:kura:*:*:*:*:*:*:*:*——Eclipse Foundation

Remediation

The sources list no fixed version for Eclipse Kura. Only install deployment packages from trusted HTTPS sources, and restrict who can install packages through the Web UI kura.packages.admin permission, the REST kura.permission.rest.deploy permission or cloud DEPLOY-V2 access.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-114359
  2. 2026-11-10 Alias added: GHSA-v72c-73r8-wfx2
  3. 2026-11-12 Priority changed: MEDIUM → LOW

References

  • TI-2023-23979 HTTP/2 request cancellation lets attackers exhaust server resources KEVCVSS 3.1HIGH 7.5
  • TI-2026-81947 Unauthenticated command injection in Eclipse Che che-machine-exec CVSS 3.1CRITICAL 9.8
  • TI-2026-13216 CWE-863: ABAC authorization bypass via trailing slash route normalization in Eclipse BaSyx Go Components CVSS 3.1CRITICAL 9.8
  • TI-2026-06514 Path traversal in Eclipse BaSyx CVSS 3.1CRITICAL 10.0
  • TI-2026-01382 In the Eclipse Theia Website repository, the GitHub Actions workflow… CVSS 3.1CRITICAL 10.0
  • TI-2026-74697 Authentication bypass in Eclipse Jetty EthereumAuthenticator CVSS 4.0CRITICAL 9.3
See all 482 →

Sources