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.
CVE-2026-13699
MEDIUMNVD 6.54.3▼Trending — 5 sources updated this week
EchelonGraph scoreMEDIUM confidence
Score 4.3 from GitHub Security Advisory published 2026-07-14. NVD baseline CVSS 6.5; sources differ by 2.2.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 4.3(medium)
- EPSS
- 14.7%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 14, 2026
Advisory Details (1)
Auto-updated Jul 14, 2026No patch confirmed yet.
generic
[Eclipse KUKSA] Databroker 0.6.1 PublishValue missing data_point panic (#148) · Issues · Eclipse Projects Security / cve-assignment · GitLab
https://gitlab.eclipse.org/security/cve-assignment/-/work_items/148Vendor Advisories for CVE-2026-13699(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 08:30 UTCEG score recompute
- 2026-07-15 08:30 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 21:22 UTCNVD updateCVSS v3 → 6.5
- 2026-07-14 08:25 UTCEG score recompute
- 2026-07-14 08:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-20
- CVE-2002-2444EG 9.8CRITICAL
- CVE-2005-0116NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2002-1359NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2000-0380NVD 0.0EG 9.0EPSS 98%NONE
- CVE-2000-0258EG 7.5EPSS 97%HIGH
- CVE-2004-2771EG 0.0EPSS 93%NONE
- CVE-2002-2443EG 0.0EPSS 93%NONE
- CVE-2002-2433EG 0.0NONE
- CVE-2003-1569EG 0.0NONE
- CVE-2003-1568EG 0.0NONE
Frequently asked(5)
What is CVE-2026-13699?
CVE-2026-13699 is a medium vulnerability published on July 14, 2026. In Eclipse KUKSA Databroker version 0.6.1, the kuksa.val.v2.VAL/PublishValue gRPC handler fails to validate the existence of the optional datapoint field in PublishValueRequest. When a request contains a valid signalid but omits datapoint, the server directly calls unwrap() on request.datapoint,…
When was CVE-2026-13699 disclosed?
CVE-2026-13699 was first published in the National Vulnerability Database on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13699 actively exploited?
CVE-2026-13699 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13699?
CVE-2026-13699 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 4.3.
How do I remediate CVE-2026-13699?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13699, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-13699
Is Your Infrastructure Affected by CVE-2026-13699?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.