# CVE-2026-1507: Uncaught Exception vulnerability in AVEVA PI Data Archive

> An unauthenticated attacker can remotely crash core PI services via an uncaught exception, causing a denial of service.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2026
- **Updated:** 12 Feb 2026
- **Also known as:** GHSA-83rc-2389-wccm

## What is CVE-2026-1507?

CVE-2026-1507 is a high-severity denial of service vulnerability in AVEVA PI Data Archive PI Server, published on 10 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The affected products are vulnerable to an uncaught exception that could allow an unauthenticated attacker to remotely crash core PI services resulting in a denial-of-service.

Weakness: CWE-248 (Uncaught Exception)

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


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

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

## Is CVE-2026-1507 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1507 is a high-severity denial of service vulnerability in AVEVA PI Data Archive PI Server, published on 10 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1507 in the wild and no public exploit code.

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

## Sources

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

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