CVE-2025-35941: mySCADA myPRO · Vulnerability
Affects mySCADA myPROSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mySCADA myPRO | Affected
| Fixed in– |
AI-suggested
Organizations should implement strict local access controls and monitoring to limit who can access systems running mySCADA myPRO version 1.3. Employing endpoint security solutions that detect unauthorized local access attempts is critical. Regularly auditing and rotating credentials used by myPRO can limit the window of opportunity for attackers. Additionally, deploying host-based intrusion detection systems (HIDS) and enforcing the principle of least privilege for local accounts can reduce the risk of exploitation. Organizations should also prepare to apply patches promptly once they become available and consider engaging with mySCADA support for any recommended interim mitigations or configuration changes. Finally, raising awareness among staff about the risks of local credential exposure and insider threats can help reduce accidental or malicious misuse.
Description
A password is exposed locally.