CVE-2026-94148: ScadaBR advisory

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

What it is

A vulnerability was determined in ScadaBR up to 1.1. Impacted is the function EmportDwr.createExportJSON of the file /ScadaBR/export_project.htm of the component Export Project Endpoint. This manipulation causes information disclosure. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 1.2.0 is recommended to address this issue. Patch name: c852b4988a15bce6011ef169299ad604538f70a9. The affected component should be upgraded. Import path was already gated with Permissions.ensureAdmin(); only export was left unprotected.

Description quoted from the CVE record (assigned by VulDB, published 2026-09-21).

Weakness: Information Disclosure; Improper Access Controls

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality low, integrity none, availability none. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 6 references on Exploit Observer

Live scores

EPSS: 0.005
low predicted chance of attack
VEDAS: 0.989
strong exploit evidence
On CISA KEV: Not listed
Detection rule: Suricata

Who is affected

Product	Affected	Not affected
ScadaBR	version 1.0 version 1.1	1.2.0 is not affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Vendor guidance:

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-94148 ScadaBR - Unauthenticated Project Export Information Disclosure. Add them to your Suricata rule set and reload.

Show the rules

suricata

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-94148 ScadaBR - Unauthenticated Project Export Information Disclosure"; flow:established,to_server; http.uri; content:"EmportDwr.createExportJSON"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-94148; reference:url,https://www.exploit.observer/?keyword=CVE-2026-94148&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=scadabr&match=exact; sid:1086001; rev:1;)

CVE-2026-94148.rules on GitHub

References

Vendor advisories and patches

Technical analysis and advisories

VDB-408062 | ScadaBR Export Project Endpoint export_project.htm EmportDwr.createExportJSON information disclosure (vdb-entry, technical-description)
CVE-2026-94148 | CVE Analysis and Report (third-party-advisory)
Submit #894000 | ScadaBR 0.9.1 Authentication Bypass Using Alternate Channel (third-party-advisory)

Other references

VDB-408062 | CTI Indicators (IOB, IOC, TTP, IOA) (signature, permissions-required)
https://github.com/ScadaBR/ScadaBR/ (product)

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.