CVE-2026-6272 Missing authorization in Eclipse KUKSA - Databroker
Attackers with read-only access can register as signal providers to inject forged data into the Eclipse KUKSA Databroker, compromising data integrity.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-6272?
CVE-2026-6272 is a high-severity missing authorization vulnerability in Eclipse KUKSA - Databroker, published on 24 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-306
Which versions are affected by CVE-2026-6272?
How do I fix CVE-2026-6272?
No fix has been published for CVE-2026-6272 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-6272 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6272 exists.
Sources
Also known as GHSA-66v8-c34p-jmrm.