Improper input validation in Eclipse Kuksa
CVE-2026-13699
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.
Vulnerability class: Drupalgeddon 2 (CVE-2018-7600)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L.
EPSS exploit prediction
EPSS: 0.004 (32.4th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 32nd percentile — 32.4% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.004 · newest: 0.004 · change: 0.000
Affected products
- Eclipse Kuksa — versions 0.6.1
- Eclipse Foundation Kuksa - Databroker — versions 0.6.1
Weakness classification (CWE)
References
- gitlab.eclipse.org/security/cve-assignment/-/work_items/148 (Issue Tracking)
Frequently asked questions
- What is CVE-2026-13699?
- CVE-2026-13699 is a medium-severity vulnerability in Eclipse Kuksa, classified under Improper Input Validation. CVSS score: 4.3/10. Published 2026-07-14.
- How severe is CVE-2026-13699?
- Medium severity. CVSS v3 base score is 4.3 out of 10.