High Cryptography

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 Sep 8, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: icscert

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

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

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

AVEVA

Pipeline Integrity Monitor

CVSS base

8.4

High · 2 source(s)

CISA SSVC assessment CISA

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

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (AVEVA Pipeline Integrity Monitor).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (cryptography), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
AVEVA	Pipeline Integrity Monitor	≤ Versions 2025 SP1 P1 (build 7.1.9580.8513)	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Every base score collected

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

Score	Version	Severity	Expl.	Impact	Scored by
8.3	CVSS 4.0	High	—	—	ics-cert@hq.dhs.gov via NIST National Vulnerability Database
8.3	CVSS 4.0	High	—	—	icscert via CVE Program (cve.org) e CISA ADP
8.4	CVSS 3.1	High	2.0	5.8	ics-cert@hq.dhs.gov via NIST National Vulnerability Database
8.4	CVSS 3.1	High	—	—	icscert via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N (score shown at the top: ics-cert@hq.dhs.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-327 · Use of a Broken or Risky Cryptographic Algorithm

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Check TLS negotiations and unexpected certificates in the component’s traffic.

endpoint telemetry (EDR)network IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Affected products added · aveva/pipeline integrity monitor
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
CVSS changed · 8.4
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Deferred
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 8, 2026 · icscert

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

3 on the record

www.cisa.gov/news-events/ics-advisories/icsa-26-253-01
NIST National Vulnerability Database
github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-253-01.jso
NIST National Vulnerability Database
www.aveva.com/content/dam/aveva/documents/support/cyber-security-updates/SecurityBu
NIST National Vulnerability Database

Elsewhere on this site

AVEVA
every CVE for this vendor

Cryptography
same class

CWE-327
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-81821 AVEVA Pipeline Integrity Monitor Use of hard-coded cryptographic key Sep 8, 2026
Medium CVE-2026-81823 AVEVA Pipeline Integrity Monitor Missing Authorization Sep 8, 2026
Medium CVE-2026-81824 AVEVA Pipeline Integrity Monitor cross-site scripting Sep 8, 2026

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 FIRST EPSS score.
No fixed version, patch or mitigation documented.
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.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-81822 is "AVEVA Pipeline Integrity Monitor Use of a Broken or Risky Cryptographic Algorithm", rated High. It affects Pipeline Integrity Monitor (AVEVA); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.4 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.