8.5
/ 10
HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H
Description
A client holding only a read JWT scope can still register itself as a signal provider through the production kuksa.val.v2 OpenProviderStream API by sending ProvideSignalRequest.
1. Obtain any valid token with only read scope.
2. Connect to the normal production gRPC API (kuksa.val.v2).
3. Open OpenProviderStream.
4. Send ProvideSignalRequest for a target signal ID.
5. Wait for the broker to forward GetProviderValueRequest.
6. Reply with attacker-controlled GetProviderValueResponse.
7. Other clients performing GetValue / GetValues for that signal receive forged data.
1. Obtain any valid token with only read scope.
2. Connect to the normal production gRPC API (kuksa.val.v2).
3. Open OpenProviderStream.
4. Send ProvideSignalRequest for a target signal ID.
5. Wait for the broker to forward GetProviderValueRequest.
6. Reply with attacker-controlled GetProviderValueResponse.
7. Other clients performing GetValue / GetValues for that signal receive forged data.
AI Analysis
A vulnerability in Eclipse KUKSA - Databroker allows an attacker with a read-only JWT scope to register as a signal provider and send forged data to other clients.
Basic Information
ID
CVE-2026-6272
Source
eclipse
Published
Apr 24, 2026 at 08:28
Affected Product
Vendor
Eclipse Foundation
Product
Eclipse KUKSA - Databroker
Version
0.5.0
Affected Versions
Eclipse Foundation Eclipse KUKSA - Databroker 0.5.0
CWE Classification
AI Assessment
AI Score
8.5 / 10
AI Severity
High
Vendor
Eclipse Foundation
Product
Eclipse KUKSA - Databroker
Version
0.5.0