Eclipse Foundation Eclipse KUKSA - Databroker vulnerabilities
🔔 Create alert RSS Version checker
Published CVEs affecting Eclipse Foundation Eclipse KUKSA - Databroker: 2 record(s), with affected versions and fixes.
CVE-2026-13699
Medium · 6.5
CWE-20 Jul 14, 2026
Databroker 0.6.1 PublishValue missing data_point panic
In Eclipse KUKSA Databroker version 0.6.1, the kuksa.val.v2.VAL/PublishValue gRPC handler fails to validate the existence of the optional data_point field in PublishValueRequest. When a request contains a valid signal_id but omits data_point, the server directly calls unwrap() on request.data_point, triggering a panic in the Tokio worker thread. This issue can be triggered by any client holding a valid JWT token. Unauthenticated or invalid-token requests are rejected and do not reach the vulnerable path. The panic causes the individual gRPC call to be cancelled but does not terminate the Databroker process, which remains available for subsequent requests.
CVE-2026-6272
High · 8.5
CWE-306 Apr 24, 2026
Missing Authentication for Critical Function in Eclipse Foundation Eclipse KUKSA - Databroker
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.