CVE-2026-13699

Databroker 0.6.1 PublishValue missing data_point panic

Published Jul 14, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

In Eclipse KUKSA Databroker 0.6.1 the PublishValue gRPC handler does not verify the optional data_point field. When a request contains a valid signal_id but omits data_point, the server unwraps the field directly and triggers a panic in a Tokio worker thread. This panic cancels the individual gRPC call but leaves the overall Databroker process alive, resulting in a partial denial-of-service for the affected call. The flaw requires a client to possess a valid JWT token; unauthenticated or invalid‑token requests are rejected before reaching the vulnerable code path.

Affected Systems

The vulnerable component is Eclipse KUKSA Databroker provided by the Eclipse Foundation, specifically version 0.6.1. No other affected versions are listed.

Risk and Exploitability

The CVSS score of 4.3 indicates low severity, and the EPSS score of less than 1% denotes a very low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog, and today it does not lead to full process crash or code execution. Likely attack would be performed over the network by an authenticated client that can forge a valid JWT, derived from the description. Overall risk is considered low, but repeated induced panics could lead to degraded service availability.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Eclipse KUKSA Databroker update that includes validation for the optional data_point field if available.
  • If upgrading is not immediately possible, limit exposure by restricting access to the PublishValue gRPC endpoint to trusted networks or clients only.
  • Ensure that only authenticated clients with valid JWTs can call PublishValue, and monitor for repeated failed calls that may indicate abuse.

Generated by OpenCVE AI on July 31, 2026 at 10:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Eclipse
Eclipse kuksa - Databroker
Vendors & Products Eclipse
Eclipse kuksa - Databroker
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Databroker 0.6.1 PublishValue missing data_point panic
Weaknesses CWE-20
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L'}

Weaknesses
  • CWE-20

    Improper Input Validation

Sources

Status
PUBLISHED
Assigner
eclipse
Published
Updated
Jul 14, 2026, 12:32 PM
Reserved
Jun 29, 2026, 11:55 AM
Status
Analyzed
Published
Jul 14, 2026, 9:16 AM
Modified
Oct 24, 2026, 10:10 PM