AVEVA Pipeline Integrity Monitor Hit With Four CVEs

Four CVEs in a pipeline monitoring tool might not normally turn heads. But when two of them involve a hard-coded cryptographic key and weak password hashing in an application deployed worldwide across critical manufacturing, the operational trade-offs are worth a closer look.

CVE-2026-81821 and CVE-2026-81822 are the pair that matter most. The first gives anyone with read access to a PIMBoards project file the ability to decrypt it and view sensitive information, because the encryption key was baked into the product. The second lets that same attacker take the password hashes from those now-exposed files and brute-force them through to administrator. CISA scored both at CVSS 8.4.

The other two round out the advisory but carry less weight: CVE-2026-81823 lets an unauthenticated attacker perform read operations meant for PIMBoards users (write operations aren't affected), and CVE-2026-81824 is a stored XSS that runs arbitrary JavaScript in a socially-engineered user's browser.

The migration trap

AVEVA's fix is straightforward on paper: upgrade to Pipeline Integrity Monitor 2025 SP1 P2 and migrate old project files. But the migration switches password hashing algorithms and moves to end-user-managed encryption keys, and it's one-way. Once a file is migrated, there's no going back. That means any organization that can't immediately patch every instance faces a real dilemma about what to do with legacy backups and transient copies that remain decryptable under the old scheme.

For project files that stay behind, AVEVA's remediation guidance describes stricter read-access controls. That's the right call, but in environments where project files move across engineering workstations, contractor networks, and air-gapped systems, tracking every copy isn't trivial.

The advisory also directs organizations to require PIMBoards users to change their passwords post-migration, which matters because any password captured from an old project file before the upgrade stays useful until users rotate credentials on the new system.

Organizations running AVEVA Pipeline Integrity Monitor should inventory where PIMBoards project files live (including backups, file shares, and contractor copies) before pulling the migration trigger. Once you go forward, you can't go back. For files that won't be migrated, read-access restrictions are the only mitigation on offer.