# CVE-2026-81821: AVEVA Pipeline Integrity Monitor Use of hard-coded cryptographic key

> An attacker with file access can decrypt sensitive data in AVEVA Pipeline Integrity Monitor projects due to a hard-coded cryptographic key.

- **Severity:** High 8.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-xgr2-pj73-vrpj

## What is CVE-2026-81821?

CVE-2026-81821 is a high-severity vulnerability in AVEVA Pipeline Integrity Monitor, published on 8 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2026-81821?


## How do I fix CVE-2026-81821?

No fix has been published for CVE-2026-81821 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-81821 being exploited?

There is no known exploitation of CVE-2026-81821 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81821 and fix it if it is affected.

What it is: CVE-2026-81821 is a high-severity vulnerability in AVEVA Pipeline Integrity Monitor, published on 8 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81821 in the wild and no public exploit code.

Affected product: AVEVA Pipeline Integrity Monitor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-81821/ (Markdown: https://insights.sbomify.com/CVE-2026-81821/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81821
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81821
- OSV: https://osv.dev/vulnerability/CVE-2026-81821

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-81821/
Summaries are generated and may contain mistakes; the official description above is the record.