Skip to main content
VulnerabilityPublished

CVE-2025-4418: AVEVA PI Connector for CygNet · CWE-354

Affects AVEVA PI Connector for CygNetSource CVE Database V5

0

Not known to be exploited · CVSS 4.4 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
4.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
AVEVA PI Connector for CygNetAffected
  • =0
Fixed in–

AI-suggested

  1. Restrict and monitor privileged access rigorously: Since exploitation requires elevated privileges, enforcing strict access controls and continuous monitoring of privileged accounts can reduce risk.
  2. Implement file integrity monitoring on PI Connector local data files to detect unauthorized modifications promptly.
  3. Isolate systems running AVEVA PI Connector for CygNet from general-purpose networks to limit local access opportunities for attackers.
  4. Regularly audit and update system configurations to ensure only authorized personnel have elevated privileges.
  5. Engage with AVEVA support and subscribe to their security advisories to obtain patches or workarounds once available.
  6. Consider deploying redundant or failover systems for the PI Connector service to maintain availability in case of service disruption.
  7. Conduct incident response drills simulating connector service unavailability to prepare operational teams for rapid recovery.
  8. Use application whitelisting and endpoint protection solutions to prevent unauthorized modification of critical files. These measures go beyond generic advice by focusing on the specific attack vector (local privileged modification of files) and the operational context of ICS environments.

Description

An improper validation of integrity check value vulnerability exists in AVEVA PI Connector for CygNet Versions 1.6.14 and prior that, if exploited, could allow a miscreant with elevated privileges to modify PI Connector for CygNet local data files (cache and buffers) in a way that causes the connector service to become unresponsive.

References

Community reviews

Loading reviews…