PoC Monitor
← All CVEs
CVE-2026-81821published 8 Sep 2026 17:42 UTCData: JSON · API

AVEVA Pipeline Integrity Monitor

AVEVA Pipeline Integrity Monitor Use of hard-coded cryptographic key

The vulnerability, if exploited, could allow a miscreant with read access to PIMBoards project files to decrypt and view sensitive information.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.4high · scored by CNA · CWE-321
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

AVEVA Pipeline Integrity Monitor
  • <= Versions 2025 SP1 P1 (build 7.1.9580.8513)

Mitigation

AVEVA Pipeline Simulation media delivers AVEVA Pipeline Integrity Monitor: * All affected versions can be fixed by upgrading to AVEVA Pipeline Integrity Monitor 2025 SP1 P2 or higher: https://softwaresupportsp.aveva.com/en-US/downloads/products/details/021a26a7-200f-44eb-8cc9-cd57b7e349aa

AVEVA recommends that organizations evaluate the impact of these vulnerabilities based on their operational environment, architecture, and product implementation. Customers using affected product versions or affected PIMBoards project files should take the following actions to mitigate the risk of exploit: * Apply AVEVA Pipeline Integrity Monitor 2025 SP1 P2 Security Update and migrate old project files. * For project files that cannot be migrated (e.g. backups or transient copies), evaluate the risk of potential password leakage from these files and implement stricter read access controls to protect these unsafe files. * Require AVEVA Pipeline Integrity Monitor PIMBoards users to change their passwords. Important: PIMBoards Project Files migration from older versions to AVEVA Pipeline Integrity Monitor 2025 SP1 P2 is one-way due to the changes in password hashing algorithms and end-user managed encryption keys.

Workaround

AVEVA recommends the following general defensive measures: * Restrict Network Access: Implement host-based and/or network firewall controls on all nodes hosting the PIMBoards API to ensure that only trusted client systems are permitted to establish connections. * Apply strong Access Control Lists to all folders storing project files to ensure only trusted users have read-access. * Maintain a trusted chain-of-custody on project files during creation, modification, distribution, backups, and use.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published8 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.