CVE-2026-84859

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-09-16. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
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.

ScadaLTS 2.8.1-release-candidate build 0 is affected by an Authenticated Blind SQL Injection

The /api/events/search endpoint accepts a JSON body containing a sortBy array. The values in this array are concatenated directly into the SQL ORDER BY clause without any sanitization or parameterization. This allows authenticated users with the ROLE_USER role to perform time-based and boolean-based blind SQL injection to extract arbitrary data from the database, including password hashes of all users.

The endpoint is accessible to any authenticated user with ROLE_USER, ROLE_ADMIN, or ROLE_PUBLIC via POST /api/events/search as defined in spring-security.xml.

CVSS v3
6.5
EG Score
6.5(high)
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
28%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

ScadaLTS Multiple Vulnerabilities - Research Advisory | Tenable®

https://www.tenable.com/security/research/tra-2026-60

Vendor Advisories for CVE-2026-84859(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 20× in last 7d / 30× 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.

  1. 2026-09-25 00:42 UTCEG score recompute
  2. 2026-09-25 00:42 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-23 23:49 UTCEG score recompute
  5. 2026-09-23 23:49 UTCGHSA enrichment
  6. 2026-09-23 17:54 UTCEPSS rescore
  7. 2026-09-22 22:58 UTCEG score recompute
  8. 2026-09-22 22:57 UTCGHSA enrichment
  9. 2026-09-22 16:01 UTCEPSS rescore
  10. 2026-09-21 22:04 UTCEG score recompute
  11. 2026-09-21 22:04 UTCGHSA enrichment
  12. 2026-09-21 21:09 UTCEPSS rescore
  13. 2026-09-20 21:12 UTCEG score recompute
  14. 2026-09-20 21:12 UTCGHSA enrichment
  15. 2026-09-20 20:16 UTCEPSS rescore
  16. 2026-09-19 20:20 UTCEG score recompute
  17. 2026-09-19 20:20 UTCGHSA enrichment
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-18 19:28 UTCEG score recompute
  20. 2026-09-18 19:28 UTCGHSA enrichment
  21. 2026-09-17 19:32 UTCEPSS rescore
  22. 2026-09-17 19:27 UTCEG score recompute
  23. 2026-09-17 19:27 UTCGHSA enrichment
  24. 2026-09-17 18:47 UTCEG score recompute
  25. 2026-09-17 18:47 UTCGHSA enrichment
Show 5 more
  1. 2026-09-17 16:12 UTCEG score recompute
  2. 2026-09-17 16:12 UTCGHSA enrichment
  3. 2026-09-16 15:20 UTCEG score recompute
  4. 2026-09-16 15:01 UTCEG score recompute
  5. 2026-09-16 15:00 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-84859?
CVE-2026-84859 is a medium vulnerability published on September 16, 2026. ScadaLTS 2.8.1-release-candidate build 0 is affected by an Authenticated Blind SQL Injection The /api/events/search endpoint accepts a JSON body containing a sortBy array. The values in this array are concatenated directly into the SQL ORDER BY clause without any sanitization or parameterization.…
When was CVE-2026-84859 disclosed?
CVE-2026-84859 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84859 actively exploited?
CVE-2026-84859 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 72.4% of all scored CVEs.
What is the CVSS score of CVE-2026-84859?
CVE-2026-84859 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-84859?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84859, 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-84859

Explore →

Is Your Infrastructure Affected by CVE-2026-84859?

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

Book a Demo →Browse All CVEs