CVE-2026-6272

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

No CVSS.

Configurations

No configuration.

History

24 Apr 2026, 12:17

Type Values Removed Values Added
References () https://gitlab.eclipse.org/security/cve-assignment/-/issues/98 - () https://gitlab.eclipse.org/security/cve-assignment/-/issues/98 -

24 Apr 2026, 09:16

Type Values Removed Values Added
New CVE

Information

Published : 2026-04-24 09:16

Updated : 2026-04-24 14:39


NVD link : CVE-2026-6272

Mitre link : CVE-2026-6272

CVE.ORG link : CVE-2026-6272


JSON object : View

Products Affected

No product.

CWE
CWE-306

Missing Authentication for Critical Function