CVE-2026-6272

State: Published
Severity: 8.5 High
Published: Apr 24, 2026
Updated: Apr 24, 2026
Reserved: Apr 14, 2026

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.

Scores

CVSS	Score	Vector	Source
4.0	8.5 High	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	eclipse

Weaknesses

CWE-306 Missing Authentication for Critical Function

Affected Products

Product	Versions
Eclipse KUKSA - DatabrokerEclipse Foundation	0.5.0 through 0.6.0Affected

References

https://gitlab.eclipse.org/security/cve-assignment/-/issues/98

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.