Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Low · CVSS 2.3

How to Fix CVE-2026-1694: PcVue (Bundle Sibling)

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-1694 is a sibling vulnerability in the same vendor advisory as CVE-2026-1692. Apply the same patched build and you close both. The technical detail below is what differs.

⚡ At a glance
Severity2.3 (Low)
Actively exploited?No public listing in CISA KEV
AffectedPcVue 16.0.0 to <=16.3.3; PcVue 15.0.0 to <=15.2.13; PcVue 12.0.0
Fixed inSame patched build as CVE-2026-1692
Type (CWE)CWE-201 Insertion of Sensitive Information into Sent Data

What's different about CVE-2026-1694?

HTTP headers are added by the default configuration of IIS and ASP.net, and are not removed at the deployment phase of the webservices used by the WebVue, WebScheduler, TouchVue and SnapVue features of PcVue in version 12.0.0 through 16.3.3 included. It unnecessarily exposes sensitive information about the server configuration.

How to fix CVE-2026-1694

Apply the patched build per the primary write-up: How to Fix CVE-2026-1692. All commands, verification steps, and rollback notes for PcVue are listed there.

Frequently asked questions

Does the CVE-2026-1692 patch close CVE-2026-1694?

Yes. Both CVEs are addressed by the same vendor patch. Applying the patched build closes the full bundle.

Is CVE-2026-1694 listed in CISA KEV?

No public KEV listing at the time of this writing.

Where is the official advisory?

See https://www.pcvue.com/security/#SB2026-2

References


*Written by Sai Kiran Pandrala. Part of the PcVue bundle. Full procedure at how-to-fix-cve-2026-1692.*