Unauthenticated service crash via uncaught exception
Published Feb 10, 2026 · Updated Feb 10, 2026
Uncaught exception handling in AVEVA PI Data Archive through 2018 SP3 Patch 7 allows remote attackers to crash core PI services. AVEVA has not published the request, code locus, or invalid operation that raises the exception and escapes handling. No authentication or user interaction is required, and the bounded consequence is interruption of core PI service availability.
Summary
What happened
Uncaught exception handling in AVEVA PI Data Archive through 2018 SP3 Patch 7 allows remote attackers to crash core PI services. AVEVA has not published the request, code locus, or invalid operation that raises the exception and escapes handling. No authentication or user interaction is required, and the bounded consequence is interruption of core PI service availability.
The record
- CVE
- CVE-2026-1507
- Published
- Feb 10, 2026
- Updated
- Feb 10, 2026
- Vendor
- AVEVA
- Product
- PI Data Archive
- Classifications
- CWE-248, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 10, 2026CVE publishedPublication date reported by the CVE source.
- Feb 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2018_SP3_Patch_7
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo