CVE-2026-1507VulnerabilityPublished 10 Feb 2026Updated 12 Feb 2026

CVE-2026-1507: AVEVA PI Data Archive PI Server · Uncaught Exception

Affects AVEVA PI Data Archive PI ServerSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: None: There is no loss of integrity within 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 10 Feb 2026
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-25.

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 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
AVEVAPI Data Archive PI Server	Affected <=2018_SP3_Patch_7	Fixed in–

AI-suggested

1. Immediately implement network segmentation to isolate AVEVA PI Data Archive PI Servers from general IT networks and limit exposure to untrusted networks, including the internet. 2. Restrict access to PI Server network ports using firewalls and access control lists (ACLs) to allow only trusted hosts and management stations. 3. Monitor PI Server logs and network traffic for unusual connection attempts or service crashes that may indicate exploitation attempts. 4. Employ intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalies in PI Server communications. 5. Coordinate with AVEVA support and subscribe to official advisories to obtain patches or updates as soon as they become available. 6. Conduct regular backups of PI Server configurations and data archives to enable rapid recovery in case of service disruption. 7. Review and harden error handling and input validation configurations if customizable within the PI Server environment. 8. Limit remote access capabilities and enforce multi-factor authentication for administrative interfaces to reduce attack surface. 9. Prepare incident response plans specifically addressing denial-of-service scenarios impacting industrial data systems.

Description

The affected products are vulnerable to an uncaught exception that could allow an unauthenticated attacker to remotely crash core PI services resulting in a denial-of-service.

Impact

For European organizations, especially those in manufacturing, energy, utilities, and critical infrastructure sectors that use AVEVA PI Systems, this vulnerability poses a significant risk of operational disruption. The denial-of-service condition can halt data collection and monitoring processes, impairing decision-making and automated control systems dependent on real-time data. This can lead to production downtime, financial losses, and in some cases, safety hazards if critical systems lose visibility or control. The lack of confidentiality or integrity impact reduces the risk of data theft or manipulation, but availability loss alone can have severe consequences in industrial contexts. The vulnerability’s ease of exploitation without authentication increases the threat level, as attackers can remotely target exposed PI Servers without needing insider access. European organizations with remote access or insufficiently segmented industrial networks are particularly vulnerable. The absence of known exploits in the wild provides a window for proactive mitigation, but the high severity score underscores the urgency of addressing this issue.

References

cisa.gov/news-events/ics-advisories/icsa-26-041-03 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Feb 2026, 09:42 UTC

WeaknessesCWE-248

Technical details

References

Community reviews

Related threats