CVE-2026-1694: Server configuration details in HTTP headers

Published Feb 26, 2026
·
Updated

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.

Affected Software

3 affected components
PcVue PcVue>=12.0.0<=16.3.3
Arcinfo Pcvue>=12.0.0<=15.2.13
Arcinfo Pcvue>=16.0.0<16.3.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade PcVue to a version that resolves this vulnerability.

    Fixed in 15.2.14Patch 15.2.14900.37147
  2. Upgrade

    Upgrade PcVue to a version that resolves this vulnerability.

    Fixed in 16.3.4Patch 16.3.4902.3112
  3. Configuration

    In C:\inetpub\<SV Website>\web.config, add/ensure the custom header: <add name="Cross-Origin-Embedder-Policy" value="require-corp" />.

    IIS web.config (customHeaders/HTTP response headers) Cross-Origin-Embedder-Policy = require-corp
  4. Configuration

    In C:\inetpub\<SV Website>\web.config, add/ensure the custom header: <add name="Cross-Origin-Opener-Policy" value="same-origin" />.

    IIS web.config (customHeaders/HTTP response headers) Cross-Origin-Opener-Policy = same-origin
  5. Configuration

    In C:\inetpub\<SV Website>\web.config, add/ensure the custom header: <add name="Cross-Origin-Resource-Policy" value="same-site" />.

    IIS web.config (customHeaders/HTTP response headers) Cross-Origin-Resource-Policy = same-site
  6. Configuration

    In C:\inetpub\<SV Website>\web.config, add/ensure the custom header: <add name="Permissions-Policy" value="geolocation=(), camera=(), microphone=()" />.

    IIS web.config (customHeaders/HTTP response headers) Permissions-Policy = geolocation=(), camera=(), microphone=()
  7. Configuration

    In C:\inetpub\<SV Website>\web.config, add/ensure the custom header: <add name="Referrer-Policy" value="strict-origin-when-cross-origin" />.

    IIS web.config (customHeaders/HTTP response headers) Referrer-Policy = strict-origin-when-cross-origin
  8. Configuration

    In C:\inetpub\<SV Website>\web.config, add/ensure the custom header: <add name="Strict-Transport-Security" value="max-age=63072000; includeSubDomains; preload" />.

    IIS web.config (customHeaders/HTTP response headers) Strict-Transport-Security = max-age=63072000; includeSubDomains; preload
  9. Configuration

    In C:\inetpub\<SV Website>\web.config, add/ensure the custom header: <add name="X-Content-Type-Options" value="nosniff" />.

    IIS web.config (customHeaders/HTTP response headers) X-Content-Type-Options = nosniff
  10. Configuration

    In C:\inetpub\<SV Website>\web.config, add/ensure the custom header: <add name="X-DNS-Prefetch-Control" value="off" />.

    IIS web.config (customHeaders/HTTP response headers) X-DNS-Prefetch-Control = off
  11. Configuration

    In C:\inetpub\<SV Website>\web.config, add/ensure the custom header: <add name="X-Frame-Options" value="DENY" />.

    IIS web.config (customHeaders/HTTP response headers) X-Frame-Options = DENY
  12. Configuration

    In C:\inetpub\<SV Website>\web.config, add/ensure the custom header: <add name="X-XSS-Protection" value="0" />.

    IIS web.config (customHeaders/HTTP response headers) X-XSS-Protection = 0
  13. Configuration

    In C:\inetpub\<SV Website>\web.config, remove the HTTP header by deleting <remove name="X-Powered-By" /> (or ensuring it is configured so X-Powered-By is not returned).

    IIS web.config (customHeaders/HTTP response headers) X-Powered-By = removed
  14. Configuration

    Ensure OAuth flows are disabled for third-party web apps (default behavior) and manually enable only the required OAuth flow(s) for each authorized Client via the patched WDC settings (examples mentioned: Authorization Code flow; Authorization Code flow with PKCE; and Resource Owner Password Credentials (ROPC) flow) if required.

    PcVue Web features (WebVue/WebScheduler/TouchVue/SnapVue OAuth flows) OAuth flows for third-party web apps = disabled by default
  15. Compensating control

    Locate control system networks and remote devices behind firewalls and isolate them from business networks; minimize network exposure for all control system devices/systems and ensure they are not accessible from insecure networks.

  16. Compensating control

    When remote access is required, use secure methods such as VPNs, recognizing VPNs may have vulnerabilities and should be updated to the most current version available.

  17. Compensating control

    If the system does not require Web & Mobile features, do not install them; if required, install them only on the Web Server.

  18. Operational

    Install a patched release of the Web Deployment Console (WDC) on the IIS Web server, use it to re-deploy the Web Site, and verify the File version property of ./bin/Modules/WebDeployment/WebDeploymentConsole.exe matches the deployed release or later (and that any earlier release is no longer used).

  19. Operational

    After deploying, verify the patch was applied correctly by performing: update IIS configuration (manually update HTTP headers), update the Web Deployment Console (WDC), and re-deploy the Web Server (and ensure Web Sites have been redeployed).

  20. Operational

    Uninstall the Web Server prior to the remediation steps, as described in the verification checklist in the material.

Event History

Feb 26, 2026
CVE Published
via MITRE·07:56 AM
Data Sourced
via MITRE·07:56 AM
RemedyDescriptionWeakness
Data Sourced
via NVD·08:16 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-1694?

CVE-2026-1694 is considered a moderate severity vulnerability due to the exposure of server configuration details in HTTP headers.

2

How do I fix CVE-2026-1694?

To fix CVE-2026-1694, you need to configure your IIS and ASP.NET applications to remove unnecessary HTTP headers before deployment.

3

Which versions of PcVue are affected by CVE-2026-1694?

CVE-2026-1694 affects PcVue versions from 12.0.0 through 16.3.3.

4

What are the security implications of CVE-2026-1694?

The security implications of CVE-2026-1694 include potential information disclosure that could aid attackers in exploiting the system.

5

Is there a patch available for CVE-2026-1694?

Currently, there is no specific patch available for CVE-2026-1694, but it is advised to modify the server configuration to mitigate the risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203