# CVE-2025-36539: AVEVA PI Data Archive Uncaught Exception

> An authenticated user can trigger an uncaught exception to shut down PI Data Archive subsystems, causing a denial of service.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2025
- **Updated:** 12 Jun 2025
- **Also known as:** GHSA-q3g5-4mm2-r2q8

## What is CVE-2025-36539?

CVE-2025-36539 is a high-severity denial of service vulnerability in AVEVA PI Data Archive, published on 12 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

AVEVA PI Data Archive products 
are vulnerable to an uncaught exception that, if exploited, could allow 
an authenticated user to shut down certain necessary PI Data Archive 
subsystems, resulting in a denial of service.

Weakness: CWE-248 (Uncaught Exception)

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


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

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

## Is CVE-2025-36539 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-36539 is a high-severity denial of service vulnerability in AVEVA PI Data Archive, published on 12 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-36539 in the wild and no public exploit code.

Affected product: AVEVA PI Data Archive. 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-36539/ (Markdown: https://insights.sbomify.com/CVE-2025-36539/index.md)
```

## Sources

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

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