CVE-2026-13699

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 14, 2026

Advisory Details (1)

Auto-updated Jul 14, 2026
No 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/148

Vendor 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 15× in last 7d / 77× 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.

Showing the most recent 100 of 111 total refreshes for this CVE.

  1. 2026-08-30 05:26 UTCEG score recompute
  2. 2026-08-30 05:26 UTCGHSA enrichment
  3. 2026-08-30 01:21 UTCEPSS rescore
  4. 2026-08-28 21:40 UTCEPSS rescore
  5. 2026-08-28 02:29 UTCEG score recompute
  6. 2026-08-28 02:29 UTCGHSA enrichment
  7. 2026-08-27 14:24 UTCEPSS rescore
  8. 2026-08-27 01:59 UTCEG score recompute
  9. 2026-08-27 01:59 UTCGHSA enrichment
  10. 2026-08-26 01:57 UTCEG score recompute
  11. 2026-08-26 01:57 UTCGHSA enrichment
  12. 2026-08-25 13:48 UTCEPSS rescore
  13. 2026-08-25 00:47 UTCEG score recompute
  14. 2026-08-25 00:47 UTCGHSA enrichment
  15. 2026-08-24 00:46 UTCGHSA enrichment
  16. 2026-08-23 00:44 UTCEG score recompute
  17. 2026-08-23 00:44 UTCGHSA enrichment
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-22 00:42 UTCEG score recompute
  20. 2026-08-22 00:42 UTCGHSA enrichment
  21. 2026-08-21 23:48 UTCEPSS rescore
  22. 2026-08-21 00:40 UTCEG score recompute
  23. 2026-08-21 00:40 UTCGHSA enrichment
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 00:38 UTCEG score recompute
Show 75 more
  1. 2026-08-20 00:38 UTCGHSA enrichment
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-18 20:22 UTCEG score recompute
  4. 2026-08-18 20:22 UTCGHSA enrichment
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 17:05 UTCEG score recompute
  7. 2026-08-17 17:05 UTCGHSA enrichment
  8. 2026-08-16 17:03 UTCEG score recompute
  9. 2026-08-16 17:03 UTCGHSA enrichment
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 17:01 UTCEG score recompute
  13. 2026-08-15 17:01 UTCGHSA enrichment
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 16:58 UTCEG score recompute
  16. 2026-08-14 16:58 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 16:56 UTCGHSA enrichment
  19. 2026-08-12 16:16 UTCEG score recompute
  20. 2026-08-12 16:16 UTCGHSA enrichment
  21. 2026-08-12 13:50 UTCEPSS rescore
  22. 2026-08-11 16:14 UTCEG score recompute
  23. 2026-08-11 16:14 UTCGHSA enrichment
  24. 2026-08-11 13:42 UTCEPSS rescore
  25. 2026-08-10 23:59 UTCEPSS rescore
  26. 2026-08-10 16:12 UTCGHSA enrichment
  27. 2026-08-09 15:44 UTCEG score recompute
  28. 2026-08-09 15:44 UTCGHSA enrichment
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-08 16:37 UTCEPSS rescore
  31. 2026-08-08 15:43 UTCEG score recompute
  32. 2026-08-08 15:43 UTCGHSA enrichment
  33. 2026-08-07 15:41 UTCGHSA enrichment
  34. 2026-08-06 15:39 UTCEG score recompute
  35. 2026-08-06 15:39 UTCGHSA enrichment
  36. 2026-08-06 13:46 UTCEPSS rescore
  37. 2026-08-05 19:17 UTCEPSS rescore
  38. 2026-08-05 15:25 UTCEG score recompute
  39. 2026-08-05 15:25 UTCGHSA enrichment
  40. 2026-08-04 15:09 UTCEPSS rescore
  41. 2026-08-04 13:24 UTCEG score recompute
  42. 2026-08-04 13:24 UTCGHSA enrichment
  43. 2026-08-04 10:38 UTCEPSS rescore
  44. 2026-08-03 12:26 UTCGHSA enrichment
  45. 2026-08-02 12:21 UTCEG score recompute
  46. 2026-08-02 12:21 UTCGHSA enrichment
  47. 2026-08-02 02:26 UTCEPSS rescore
  48. 2026-08-01 12:18 UTCEG score recompute
  49. 2026-08-01 12:18 UTCGHSA enrichment
  50. 2026-08-01 04:15 UTCEPSS rescore
  51. 2026-07-31 12:15 UTCEG score recompute
  52. 2026-07-31 12:15 UTCGHSA enrichment
  53. 2026-07-30 16:27 UTCEPSS rescore
  54. 2026-07-30 12:13 UTCEG score recompute
  55. 2026-07-30 12:13 UTCGHSA enrichment
  56. 2026-07-30 01:30 UTCEPSS rescore
  57. 2026-07-29 12:10 UTCEG score recompute
  58. 2026-07-29 12:10 UTCGHSA enrichment
  59. 2026-07-28 15:36 UTCEPSS rescore
  60. 2026-07-28 12:08 UTCEG score recompute
  61. 2026-07-28 12:08 UTCGHSA enrichment
  62. 2026-07-27 14:13 UTCEPSS rescore
  63. 2026-07-27 11:53 UTCEG score recompute
  64. 2026-07-27 11:52 UTCGHSA enrichment
  65. 2026-07-26 14:54 UTCEPSS rescore
  66. 2026-07-26 14:54 UTCEPSS rescore
  67. 2026-07-26 11:49 UTCEG score recompute
  68. 2026-07-26 11:49 UTCGHSA enrichment
  69. 2026-07-25 14:17 UTCEPSS rescore
  70. 2026-07-24 14:17 UTCEPSS rescore
  71. 2026-07-23 14:18 UTCEPSS rescore
  72. 2026-07-23 03:05 UTCEG score recompute▲ 2.20
  73. 2026-07-22 14:08 UTCEPSS rescore
  74. 2026-07-21 15:24 UTCEPSS rescore
  75. 2026-07-20 17:08 UTCEPSS rescore

Related CVEs(same CWE)

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 0% probability of exploitation in the next 30 days, which ranks it in the top 67.7% of all scored CVEs.
What is the CVSS score of CVE-2026-13699?
CVE-2026-13699 has a CVSS v3 base score of 6.5 (NVD).
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

Explore →

Is Your Infrastructure Affected by CVE-2026-13699?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs