CVE Catalog

CVE-2026-6272

High
Published: Translated: NVD NIST

Summary

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. The attacker can then reply to GetProviderValueRequest with forged data, causing other clients to receive manipulated signal values.

Risk Assessment

The vulnerability allows an attacker to forge signal data, potentially leading to incorrect decisions by systems relying on that data.

Recommendation

Implement proper authorization controls so that only clients with appropriate permissions can register as signal providers.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS