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

Fri, 24 Apr 2026 08:45:00 +0000

Type Values Removed Values Added
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.
Weaknesses CWE-306
References
Metrics cvssV4_0

{'score': 8.5, 'vector': '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'}


cve-icon MITRE

Status: PUBLISHED

Assigner: eclipse

Published: 2026-04-24T08:28:17.690Z

Updated: 2026-04-24T08:28:17.690Z

Reserved: 2026-04-14T12:57:50.655Z

Link: CVE-2026-6272

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-04-24T09:16:04.227

Modified: 2026-04-24T09:16:04.227

Link: CVE-2026-6272

cve-icon Redhat

No data.