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.

CVSS v3 4.3 MEDIUM

4.3^/10

CVSS v3 : MEDIUM

Vector :

Exploitability : 2.8 / Impact : 1.4

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact LOW

Scope UNCHANGED

References

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

Configurations

Configuration 1 (hide)

cpe:2.3:a:eclipse:kuksa:0.6.1:*:*:*:*:*:*:*

History

24 Oct 2026, 22:10

Type	Values Removed	Values Added
Summary		(es) En Eclipse KUKSA Databroker versión 0.6.1, el gestor gRPC kuksa.val.v2.VAL/PublishValue no valida la existencia del campo opcional data_point en PublishValueRequest. Cuando una solicitud contiene un signal_id válido pero omite data_point, el servidor llama directamente a unwrap() en request.data_point, lo que desencadena un pánico en el hilo de trabajo de Tokio. Este problema puede ser provocado por cualquier cliente que posea un token JWT válido. Las solicitudes no autenticadas o con token inválido son rechazadas y no alcanzan la ruta vulnerable. El pánico provoca que la llamada gRPC individual sea cancelada, pero no termina el proceso de Databroker, el cual permanece disponible para solicitudes posteriores.

Information

Published : 2026-07-14 09:16

Updated : 2026-10-24 22:10

NVD link : CVE-2026-13699

Mitre link : CVE-2026-13699

CVE.ORG link : CVE-2026-13699

JSON object : View

Products Affected

eclipse

kuksa

CWE

CWE-20

Improper Input Validation

{"id": "CVE-2026-13699", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-13699", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-07-14T12:32:21.023928Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "emo@eclipse.org", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 2.8}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 2.8}]}, "affected": [{"source": "emo@eclipse.org", "affectedData": [{"vendor": "Eclipse Foundation", "product": "Eclipse KUKSA - Databroker", "versions": [{"status": "affected", "version": "0.6.1", "versionType": "semver"}], "defaultStatus": "unaffected"}]}], "published": "2026-07-14T09:16:40.050", "references": [{"url": "https://gitlab.eclipse.org/security/cve-assignment/-/work_items/148", "tags": ["Issue Tracking"], "source": "emo@eclipse.org"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "emo@eclipse.org", "description": [{"lang": "en", "value": "CWE-20"}]}], "descriptions": [{"lang": "en", "value": "In Eclipse KUKSA Databroker version 0.6.1, the\u00a0kuksa.val.v2.VAL/PublishValue\u00a0gRPC handler fails to validate the existence of the optional\u00a0data_point\u00a0field in\u00a0PublishValueRequest. When a request contains a valid\u00a0signal_id\u00a0but omits\u00a0data_point, the server directly calls\u00a0unwrap()\u00a0on\u00a0request.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."}, {"lang": "es", "value": "En Eclipse KUKSA Databroker versi\u00f3n 0.6.1, el gestor gRPC kuksa.val.v2.VAL/PublishValue no valida la existencia del campo opcional data_point en PublishValueRequest. Cuando una solicitud contiene un signal_id v\u00e1lido pero omite data_point, el servidor llama directamente a unwrap() en request.data_point, lo que desencadena un p\u00e1nico en el hilo de trabajo de Tokio. Este problema puede ser provocado por cualquier cliente que posea un token JWT v\u00e1lido. Las solicitudes no autenticadas o con token inv\u00e1lido son rechazadas y no alcanzan la ruta vulnerable. El p\u00e1nico provoca que la llamada gRPC individual sea cancelada, pero no termina el proceso de Databroker, el cual permanece disponible para solicitudes posteriores."}], "lastModified": "2026-10-24T22:10:00.210", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:eclipse:kuksa:0.6.1:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "5606BBD7-9796-4EEF-B949-A2E87C3625D7"}], "operator": "OR"}]}], "sourceIdentifier": "emo@eclipse.org"}