Read the docs

Incorrect authorization in Eclipse Kura wire component updates

Priority LOW 34CWE-807Published · Updated

Key facts

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

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

Summary

Eclipse Kura versions 5.0.0 through 5.6.2 are affected. The Wire Graph update and Wire Service REST API v1 use the request's factory identifier to find the target component, not its actual factory (CWE-863). An authenticated user with only the Wires management permission can alter or replace existing components, including security-relevant ones, which allows escalation to full administrative privileges. Modifying arbitrary components requires a Driver installed on the device.

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

Description from the CNA

In Eclipse Kura versions 5.0.0 through 5.6.2, the Wire Graph update functionality of the Kura Web UI, and the Wire Service REST API v1 (available since 5.1.0, org.eclipse.kura.rest.wire.provider), determine whether a configuration update targets a Wire Component, Driver or Asset from the factory identifier supplied in the request, instead of the actual factory of the existing component. An authenticated identity holding only the Wires management permission (kura.wires.admin for the Web UI, rest.wires.admin for the REST API) can therefore modify the configuration of existing components that are not part of the Wire Graph, including security-relevant ones, or replace existing components. This allows escalation to full administrative privileges and can disrupt the device. Modifying arbitrary components requires at least one Driver to be installed on the device. The issue is fixed in Eclipse Kura 5.6.3.

Why it matters now

EPSS 0.00357 29th 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 Kura5.0.0 – 5.6.2—No fix listedCNA
  • Eclipse Kura VendorEclipse Foundation Affected 5.0.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

Upgrade Eclipse Kura to version 5.6.3, which fixes the issue.

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

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-113422
  2. 2026-11-10 Alias added: GHSA-g9qx-c69p-gqxc
  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