CVE-2026-13699 Databroker 0.6.1 PublishValue missing data_point panic
Authenticated attackers can cause a panic in the Databroker gRPC handler by omitting a required field, leading to a denial of service for that specific request.
- 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-13699?
CVE-2026-13699 is a medium-severity vulnerability in Eclipse KUKSA - Databroker, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
In Eclipse KUKSA Databroker version 0.6.1, the kuksa.val.v2.VAL/PublishValue gRPC handler fails to validate the existence of the optional data_point field in PublishValueRequest. When a request contains a valid signal_id but omits data_point, the server directly calls unwrap() on request.data_point, triggering a panic in the Tokio worker thread. This issue can be triggered by any client holding a valid JWT token. Unauthenticated or invalid-token requests are rejected and do not reach the vulnerable path. The panic causes the individual gRPC call to be cancelled but does not terminate the Databroker process, which remains available for subsequent requests.
Weakness: CWE-20
Which versions are affected by CVE-2026-13699?
It affects 1 product.
Products include Eclipse Kuksa.
How do I fix CVE-2026-13699?
No fix has been published for CVE-2026-13699 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-13699 being exploited?
There is no known exploitation of CVE-2026-13699 in the wild and no public exploit code.
Sources
Also known as GHSA-ccmw-x5fc-v2mm.