Is CVE-2026-13699 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-13699 being exploited in the wild.

How severe is CVE-2026-13699?

Medium severity, with a CVSS score of 4.3, published 14 July 2026.

Which products and versions are affected?

Eclipse Foundation KUKSA Databroker 0.6.1.

Is there a fix for CVE-2026-13699?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-13699 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-13699?

Check whether you run Eclipse Foundation KUKSA Databroker at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-13699: Eclipse KUKSA Databroker thread panic in PublishValue gRPC handler

CVE-2026-13699 · Severity: medium · CVSS 4.3 · Published 2026-07-14

Eclipse KUKSA Databroker, a component used for managing vehicle data in automotive software, contains a flaw in how it handles certain data update requests. An authorized user can send a specifically crafted message that causes a portion of the service to crash. While the entire system does not shut down, it can lead to failed data transmissions and minor service disruptions.

Vendors: Eclipse Foundation.

Quick answers

Is CVE-2026-13699 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-13699 being exploited in the wild.
How severe is CVE-2026-13699?: Medium severity, with a CVSS score of 4.3, published 14 July 2026.
Which products and versions are affected?: Eclipse Foundation KUKSA Databroker 0.6.1.
Is there a fix for CVE-2026-13699?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-13699 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-13699?: Check whether you run Eclipse Foundation KUKSA Databroker at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an improper input validation issue (CWE-20) within the `kuksa.val.v2.VAL/PublishValue` gRPC handler of Eclipse KUKSA Databroker. The server implementation calls `unwrap()` on the optional `data_point` field in a `PublishValueRequest` without first verifying its presence. If a request includes a valid `signal_id` but omits the `data_point`, the resulting panic in the Tokio worker thread causes the specific gRPC call to fail. Exploitation requires the attacker to possess a valid JWT token; unauthenticated requests are blocked before reaching the vulnerable code path. While the individual thread panics, the main Databroker process remains operational.

Affected products

Eclipse Foundation KUKSA Databroker 0.6.1

Timeline

2026-07-14: advisory: NVD and Eclipse Foundation published the advisory.

References

https://gitlab.eclipse.org/security/cve-assignment/-/work_items/148

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.