CVE-2026-113422 · Runtime
NO FIX YET · SEE WHAT TO DO
Eclipse Kura's Web UI and Wire Service REST API trust the factory identifier in a configuration update instead of the existing component's real factory. A user holding only the Wires management permission can change or replace unrelated components, including security-relevant ones, which can lead to full administrative privileges.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Devices running Eclipse Kura from 5.0.0 through 5.6.2 are exposed, and exploitation needs an account holding the Wires management permission (kura.wires.admin or rest.wires.admin). Exploitation of arbitrary components requires at least one Driver to be installed. Teams not running Kura on their devices can skip it.
Not affected if kura-5.6.3-or-later, kura-below-5.0.0, no-wires-permission-users
Who cares eclipse-kura, industrial-gateway, iot, rest-api
5.0.0 through 5.6.2 are in range.org.eclipse.kura.rest.wire.provider, from 5.1.0) or the Web UI Wire Graph is in use.5.6.3In 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.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.