Sensitive-data decryption via hard-coded project-file key
Published Sep 8, 2026 · Updated Sep 8, 2026
Hard-coded cryptography in AVEVA Pipeline Integrity Monitor 2025 SP1 P1 and earlier allows local users to decrypt sensitive PIMBoards project data. PIMBoards encrypts project-file contents with key material embedded in the product, making the same key available for recovering protected information. Exploitation requires low-privileged local read access to an affected project file; the demonstrated consequence is disclosure of its protected contents.
Summary
What happened
Hard-coded cryptography in AVEVA Pipeline Integrity Monitor 2025 SP1 P1 and earlier allows local users to decrypt sensitive PIMBoards project data. PIMBoards encrypts project-file contents with key material embedded in the product, making the same key available for recovering protected information. Exploitation requires low-privileged local read access to an affected project file; the demonstrated consequence is disclosure of its protected contents.
The record
- CVE
- CVE-2026-81821
- Published
- Sep 8, 2026
- Updated
- Sep 8, 2026
- Vendor
- AVEVA
- Product
- AVEVA Pipeline Integrity Monitor
- Classifications
- CWE-321, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 8, 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 <=Versions 2025 SP1 P1 (build 7.1.9580.8513)
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