Skip to content
Heist/ feed
Back to feed
Medium

Databroker 0.6.1 PublishValue missing data_point panic

Type: advisorySources: OSV

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.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-13699
Confirmed fixed CVEs
Not specified
Updated in this feed
5 Nov 2026, 00:55 UTC · Revision 1

Source evidence

Databroker 0.6.1 PublishValue missing data_point panic

core-osv · Original source

Published 14 Jul 2026, 07:38 UTC

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.

osv:CVE-2026-13699
Complete source record
{
  "id": "177a7874cd5cb40fc3a91c92e221aa52ad41e3cdac15ee66302356588a2cf0cd",
  "url": "https://osv.dev/vulnerability/CVE-2026-13699",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Databroker 0.6.1 PublishValue missing data_point panic",
    "summary": "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.",
    "evidence": "osv:CVE-2026-13699",
    "products": [],
    "severity": "medium",
    "structured": {
      "id": "CVE-2026-13699",
      "aliases": [
        "CVE-2026-13699"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/eclipse-kuksa/kuksa-databroker",
              "type": "GIT",
              "events": [
                {
                  "introduced": "dd9cb5d1c2da2543dd3b3aa7e5fb350d07412c66"
                },
                {
                  "last_affected": "dd9cb5d1c2da2543dd3b3aa7e5fb350d07412c66"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "cpe": "cpe:2.3:a:eclipse:kuksa:0.6.1:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "0.6.1"
                      },
                      {
                        "last_affected": "0.6.1"
                      }
                    ],
                    "source": "CPE_STRING"
                  }
                ]
              }
            }
          ],
          "versions": [
            "0.6.1"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-13699.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:41.051820616Z",
      "provider": "osv",
      "references": [
        "https://gitlab.eclipse.org/security/cve-assignment/-/work_items/148",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/13xxx/CVE-2026-13699.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-13699"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-20"
        ],
        "cna_assigner": "eclipse",
        "unresolved_ranges": [
          {
            "extracted_events": [
              {
                "range": [
                  {
                    "introduced": "0.6.1"
                  },
                  {
                    "last_affected": "0.6.1"
                  }
                ],
                "source": "AFFECTED_FIELD",
                "strategy": "StandaloneSingleVersion"
              }
            ]
          }
        ],
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/13xxx/CVE-2026-13699.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-13699",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 508753,
  "published_at": "2026-07-14T07:38:23.271+00:00"
}