CVE-2026-13699: CWE-20: Improper Input Validation in Eclipse Foundation Eclipse KUKSA - Databroker
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.
AI Analysis
Technical Summary
CVE-2026-13699 is an input validation vulnerability (CWE-20) in Eclipse KUKSA Databroker version 0.6.1. The vulnerability arises because the PublishValue gRPC handler does not validate the existence of the optional data_point field in PublishValueRequest messages. When a request with a valid signal_id omits data_point, the server calls unwrap() on the absent data_point, causing a panic in the Tokio worker thread. This results in the cancellation of the affected gRPC call but does not terminate the Databroker service. Exploitation requires a valid JWT token; unauthenticated or invalid-token requests are blocked before the vulnerable code is reached. No patch or official remediation is currently documented.
Potential Impact
An attacker with a valid JWT token can cause a denial of service for individual gRPC calls by triggering a panic in the Tokio worker thread. The panic cancels only the specific gRPC call but does not crash or stop the Databroker process, which remains available for other requests. There is no impact on confidentiality or integrity reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to clients with valid JWT tokens and monitor for abnormal gRPC call cancellations. No official fix or workaround is documented at this time.
CVE-2026-13699: CWE-20: Improper Input Validation in Eclipse Foundation Eclipse KUKSA - Databroker
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 v3.1
Score 4.3medium
Affected software
pkg:github/eclipse/kuksa-databrokerRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-13699 is an input validation vulnerability (CWE-20) in Eclipse KUKSA Databroker version 0.6.1. The vulnerability arises because the PublishValue gRPC handler does not validate the existence of the optional data_point field in PublishValueRequest messages. When a request with a valid signal_id omits data_point, the server calls unwrap() on the absent data_point, causing a panic in the Tokio worker thread. This results in the cancellation of the affected gRPC call but does not terminate the Databroker service. Exploitation requires a valid JWT token; unauthenticated or invalid-token requests are blocked before the vulnerable code is reached. No patch or official remediation is currently documented.
Potential Impact
An attacker with a valid JWT token can cause a denial of service for individual gRPC calls by triggering a panic in the Tokio worker thread. The panic cancels only the specific gRPC call but does not crash or stop the Databroker process, which remains available for other requests. There is no impact on confidentiality or integrity reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to clients with valid JWT tokens and monitor for abnormal gRPC call cancellations. No official fix or workaround is documented at this time.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- eclipse
- Date Reserved
- 2026-06-29T11:55:12.660Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a55f44d68715ace431bbf2d
Added to database: 07/14/2026, 08:33:17 UTC
Last enriched: 07/14/2026, 08:48:02 UTC
Last updated: 07/14/2026, 09:18:34 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.