# CVE-2026-13699: Databroker 0.6.1 PublishValue missing data_point panic

> Authenticated attackers can cause a panic in the Databroker gRPC handler by omitting a required field, leading to a denial of service for that specific request.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-ccmw-x5fc-v2mm

## What is CVE-2026-13699?

CVE-2026-13699 is a medium-severity vulnerability in Eclipse KUKSA - Databroker, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-13699?

It affects 1 product.


Products: Eclipse Kuksa.

## How do I fix CVE-2026-13699?

No fix has been published for CVE-2026-13699 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13699 being exploited?

There is no known exploitation of CVE-2026-13699 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13699 and fix it if it is affected.

What it is: CVE-2026-13699 is a medium-severity vulnerability in Eclipse KUKSA - Databroker, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-13699 in the wild and no public exploit code.

Affected product: Eclipse KUKSA - Databroker. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13699/ (Markdown: https://insights.sbomify.com/CVE-2026-13699/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13699
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13699
- OSV: https://osv.dev/vulnerability/CVE-2026-13699

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13699/
Summaries are generated and may contain mistakes; the official description above is the record.