CVE Intelligence
Skip to main content
HIGH

CVE-2026-81822

CVE-2026-81822 — AVEVA Pipeline Integrity Monitor Use of a Broken or Risky Cryptographic Algorithm

The vulnerability, if exploited, could allow a miscreant with read access to PIMBoards project files to reverse engineer PIMBoards users’ app-native passwords through computational brute-forcing of weak hashes, potentially allowing elevation to a PIMBoards administrator user.

Published Updated Sources: cvelistV5, icscert

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

aveva

pipeline_integrity_monitor

CVSS base

8.4

HIGH

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

aveva

Products (1)

pipeline integrity monitor

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
8.4CVSS 3.1HIGH——cvelistV5

Weakness & attack patterns

  • CWE-327

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1036.001Masquerading: Invalid Code Signature
  • T1553.002Subvert Trust Controls: Code Signing

References

3 on the record

Elsewhere on this site

  • avevaevery CVE for this vendor
  • CWE-327other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.