# CVE-2025-4418: AVEVA PI Connector for CygNet Improper Validation of Integrity Check Value


- **Severity:** Medium 6.7 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 Jun 2025
- **Updated:** 12 Jun 2025
- **Also known as:** GHSA-mqm6-5rhf-vp27

## What is CVE-2025-4418?

CVE-2025-4418 is a medium-severity vulnerability in AVEVA PI Connector for CygNet, published on 12 Jun 2025. 

### Official description

An improper validation of integrity check value vulnerability exists in 

AVEVA PI Connector for CygNet Versions 1.6.14 and prior that, if exploited, 
could allow a miscreant with elevated privileges to modify PI Connector 
for CygNet local data files (cache and buffers) in a way that causes the
 connector service to become unresponsive.

Weakness: CWE-354 (Improper Validation of Integrity Check Value)

## Which versions are affected by CVE-2025-4418?


## How do I fix CVE-2025-4418?

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

## Is CVE-2025-4418 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4418 and fix it if it is affected.

What it is: CVE-2025-4418 is a medium-severity vulnerability in AVEVA PI Connector for CygNet, published on 12 Jun 2025. 
Exploitation: There is no known exploitation of CVE-2025-4418 in the wild and no public exploit code.

Affected product: AVEVA PI Connector for CygNet. 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-2025-4418/ (Markdown: https://insights.sbomify.com/CVE-2025-4418/index.md)
```

## Sources

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

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