CVE-2026-13699 — MEDIUM (4.3)

Vulnerability 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.

CVSS Score

4.3

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

LOW

User Interaction

NONE

Scope

UNCHANGED

Confidentiality

NONE

Integrity

NONE

Availability

LOW

Affected Products

Vendor	Product	Versions
Eclipse	Kuksa	0.6.1

Related Weaknesses (CWE)

CWE-20

References

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

FAQ

What is CVE-2026-13699?

CVE-2026-13699 is a vulnerability with a CVSS score of 4.3 (MEDIUM). 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 contai...

How severe is CVE-2026-13699?

CVE-2026-13699 has been rated MEDIUM with a CVSS base score of 4.3/10. Review the CVSS metrics above for detailed severity breakdown.

Is there a patch for CVE-2026-13699?

Check the references section above for vendor advisories and patch information. Affected products include: Eclipse Kuksa.