# CVE-2026-28698: Exposure of Sensitive System Information to an Unauthorized Control Sphere in Panduit IntraVUE by Pronetiqs

> Attackers can access sensitive system information and underlying host filesystems in Pronetiqs IntraVUE, requiring an upgrade to secure industrial control environments.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/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:** 23 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-f6pj-m25g-9pq4

## What is CVE-2026-28698?

CVE-2026-28698 is a critical vulnerability in Pronetiqs Panduit Intravue, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could expose the underlying host/share filesystem.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2026-28698 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28698 is a critical vulnerability in Pronetiqs Panduit Intravue, published on 23 Jul 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-28698 in the wild and no public exploit code.

Affected product: Pronetiqs Panduit Intravue. 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-28698/ (Markdown: https://insights.sbomify.com/CVE-2026-28698/index.md)
```

## Sources

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

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