Quick answers
- Is CVE-2026-84859 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84859 being exploited in the wild.
- How severe is CVE-2026-84859?
- Medium severity, with a CVSS score of 6.5, published 16 September 2026.
- Which products and versions are affected?
- ScadaLTS 2.8.1-release-candidate build 0.
- Is there a fix for CVE-2026-84859?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-84859 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-84859?
- Check whether you run ScadaLTS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The /api/events/search endpoint accepts a JSON body with a sortBy array whose values are concatenated directly into the SQL ORDER BY clause without sanitization or parameterization. Authenticated users with ROLE_USER, ROLE_ADMIN, or ROLE_PUBLIC can exploit this via time-based or boolean-based blind SQL injection to extract arbitrary database contents, including user password hashes. The attack requires that the authenticated user has at least one visible event in the userEvents table, which is the normal operational state for any SCADA operator with data-point or data-source event subscriptions. No patch is available at the time of publication.
Affected products
- ScadaLTS ScadaLTS 2.8.1-release-candidate build 0
Timeline
- 2026-09-16: disclosed