VulnerabilityPublished 12 Jun 2025

CVE-2025-44019: AVEVA PI Data Archive · CWE-248

Affects AVEVA PI Data ArchiveSource CVE Database V5

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
AVEVA PI Data Archive	Affected =0	Fixed in–

AI-suggested

Implement strict access controls and monitoring on AVEVA PI Data Archive systems to limit authenticated user access only to trusted personnel and services.
Employ network segmentation and isolation for OT environments hosting PI Data Archive to reduce exposure to compromised accounts or external attackers.
Monitor system logs and alerts for unusual shutdowns or subsystem failures indicative of exploitation attempts.
Develop and test incident response plans specifically for PI Data Archive service disruptions to minimize downtime and data loss.
Coordinate with AVEVA for timely patch releases and apply updates as soon as they become available.
Consider deploying application-layer protections such as input validation or exception handling wrappers if feasible to reduce uncaught exception risks.
Conduct regular backups of critical snapshot and cache data to enable recovery in case of data loss.
Train operational staff on recognizing and reporting suspicious activity related to PI Data Archive access.
Use multi-factor authentication (MFA) to strengthen authentication mechanisms and reduce risk of credential compromise.
Perform vulnerability scanning and penetration testing focused on PI Data Archive to identify and remediate related security gaps.

Description

AVEVA PI Data Archive products are vulnerable to an uncaught exception that, if exploited, could allow an authenticated user to shut down certain necessary PI Data Archive subsystems, resulting in a denial of service. Depending on the timing of the crash, data present in snapshots/write cache may be lost.

Impact

For European organizations, the impact of CVE-2025-44019 can be significant, especially those relying on AVEVA PI Data Archive for industrial process data management. The denial of service caused by subsystem shutdowns can interrupt critical industrial operations, potentially halting production lines, disrupting energy distribution, or affecting water and utility services. The risk of data loss during snapshot or cache writes could impair operational decision-making, compliance reporting, and historical data analysis. This can lead to financial losses, safety risks, and regulatory non-compliance. Given the reliance of many European industries on real-time data for automation and monitoring, availability disruptions can cascade into broader operational outages. The requirement for authenticated access limits exploitation to insiders or compromised accounts, but insider threats or lateral movement by attackers within networks remain a concern. The lack of confidentiality impact reduces risk of data leakage but does not mitigate operational risks. The absence of known exploits suggests a window for proactive mitigation before active attacks emerge.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Jun 2025, 20:23 UTC

WeaknessesCWE-248

Technical details

References

Community reviews

Related threats