CVE-2026-94148: ScadaBR information disclosure in export project endpoint

CVE-2026-94148 · Severity: medium · CVSS 5.3 · Published 2026-09-21

ScadaBR is an open-source SCADA (supervisory control and data acquisition) system used to monitor and control industrial processes. A vulnerability in the project export function allows authenticated attackers to extract sensitive project data without proper authorization checks. While the import function was protected with admin-level access controls, the export function was left unprotected, enabling unauthorized information disclosure.

Vendors: ScadaBR.

Quick answers

Is CVE-2026-94148 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-94148 being exploited in the wild.
How severe is CVE-2026-94148?
Medium severity, with a CVSS score of 5.3, published 21 September 2026.
Which products and versions are affected?
ScadaBR up to 1.1.
Is there a fix for CVE-2026-94148?
A patch was published on 2026-09-21: Fixed in version 1.2.0 (commit c852b49) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-94148 attacked?
It is attacked over the network.
Am I affected by CVE-2026-94148?
Check whether you run ScadaBR 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 EmportDwr.createExportJSON function in the /ScadaBR/export_project.htm endpoint fails to enforce access controls, allowing information disclosure through project export. The vulnerability is an authorization bypass where admin-level permission checks were implemented for import but not for export. Attackers with network access can trigger the export function to retrieve sensitive configuration and operational data; a patch is available in version 1.2.0.

Affected products

  • ScadaBR ScadaBR up to 1.1

Timeline

  • 2026-09-21: disclosed
  • 2026-09-21: patched: Fixed in version 1.2.0 (commit c852b49)

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.