Vulnerability 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.
Related Weaknesses (CWE)
References
- https://gitlab.eclipse.org/security/cve-assignment/-/issues/98
- https://gitlab.eclipse.org/security/cve-assignment/-/issues/98
FAQ
What is CVE-2026-6272?
CVE-2026-6272 is a documented vulnerability. 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 t...
How severe is CVE-2026-6272?
CVSS scoring is not yet available for CVE-2026-6272. Check NVD for updates.
Is there a patch for CVE-2026-6272?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.