CVE-2026-13699 in Eclipse KUKSA Databroker
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.
Quick answer
Eclipse Foundation Eclipse KUKSA Databroker should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Eclipse KUKSA Databroker 0.6.1
Fixed versions
- Latest vendor-supported patched release or mitigation listed in the Eclipse advisory
How to fix it
CVE-2026-13699 affects Eclipse KUKSA Databroker. In simple terms, a person without the right login may reach a protected action. Fix it by updating to Latest vendor-supported patched release or mitigation listed in the Eclipse advisory. If this system is online or used by admins, treat the fix as important.
- Find every place where Eclipse KUKSA Databroker is installed or used.
- Check if the version matches: Eclipse KUKSA Databroker 0.6.1.
- Update or apply the vendor fix: Latest vendor-supported patched release or mitigation listed in the Eclipse advisory.
- If you cannot update today, allow only trusted users and trusted networks.
- Turn off the affected feature or plugin if the vendor says that is safe to do.
- Check logs for crashes, strange requests, new admin actions, or unexpected access.
- Change secrets or passwords if you think data or admin access may have been exposed.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version or mitigation matches: Latest vendor-supported patched release or mitigation listed in the Eclipse advisory.
- Confirm the affected feature is no longer exposed to untrusted users.
- Run the affected workflow again and make sure it still works.
- Review logs again after the fix for repeated suspicious activity.
- Run a new Fixnx scan if this software is part of a public website.
- Save the advisory link and proof of the fix in your change record.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-13699?
Eclipse Foundation Eclipse KUKSA Databroker versions listed as affected should be reviewed: Eclipse KUKSA Databroker 0.6.1.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.