CVE-2026-1696: Missing security HTTP headers
Some HTTP security headers are not properly set by the web server when sending responses to the client application.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Open C:\inetpub\<SV Website>\web.config and add in the customHeaders section: <add name="Cross-Origin-Embedder-Policy" value="require-corp" />
IIS web.config (SV Website) customHeaders: Cross-Origin-Embedder-Policy = require-corp - Configuration
Open C:\inetpub\<SV Website>\web.config and add in the customHeaders section: <add name="Cross-Origin-Opener-Policy" value="same-origin" />
IIS web.config (SV Website) customHeaders: Cross-Origin-Opener-Policy = same-origin - Configuration
Open C:\inetpub\<SV Website>\web.config and add in the customHeaders section: <add name="Cross-Origin-Resource-Policy" value="same-site" />
IIS web.config (SV Website) customHeaders: Cross-Origin-Resource-Policy = same-site - Configuration
Open C:\inetpub\<SV Website>\web.config and add in the customHeaders section: <add name="Permissions-Policy" value="geolocation=(), camera=(), microphone=()" />
IIS web.config (SV Website) customHeaders: Permissions-Policy = geolocation=(), camera=(), microphone=() - Configuration
Open C:\inetpub\<SV Website>\web.config and add in the customHeaders section: <add name="Referrer-Policy" value="strict-origin-when-cross-origin" />
IIS web.config (SV Website) customHeaders: Referrer-Policy = strict-origin-when-cross-origin - Configuration
Open C:\inetpub\<SV Website>\web.config and add in the customHeaders section: <add name="Strict-Transport-Security" value="max-age=63072000; includeSubDomains; preload" />
IIS web.config (SV Website) customHeaders: Strict-Transport-Security = max-age=63072000; includeSubDomains; preload - Configuration
Open C:\inetpub\<SV Website>\web.config and add in the customHeaders section: <add name="X-Content-Type-Options" value="nosniff" />
IIS web.config (SV Website) customHeaders: X-Content-Type-Options = nosniff - Configuration
Open C:\inetpub\<SV Website>\web.config and add in the customHeaders section: <add name="X-DNS-Prefetch-Control" value="off" />
IIS web.config (SV Website) customHeaders: X-DNS-Prefetch-Control = off - Configuration
Open C:\inetpub\<SV Website>\web.config and add in the customHeaders section: <add name="X-Frame-Options" value="DENY" />
IIS web.config (SV Website) customHeaders: X-Frame-Options = DENY - Configuration
Open C:\inetpub\<SV Website>\web.config and add in the customHeaders section: <add name="X-XSS-Protection" value="0" />
IIS web.config (SV Website) customHeaders: X-XSS-Protection = 0 - Configuration
Open C:\inetpub\<SV Website>\web.config and remove the header entry: <remove name="X-Powered-By" />
IIS web.config (SV Website) customHeaders/remove: X-Powered-By = removed - Configuration
Ensure that, in the patched release of the Web Deployment Console (WDC), all OAuth flows are disabled for third-party web apps by default; manually enable the specific flow(s) per authorized Client only if required.
OAuth configuration (Web & Mobile features / WDC patched settings) OAuth flows for third-party web apps = disabled by default - Configuration
Using the patched release of the Web Deployment Console (WDC) on the IIS Web server, set the new per-authorized-Client setting for the Authorization Code flow to enable or disable as required.
OAuth configuration (WDC patched settings) Authorization Code flow = enable/disable per authorized Client - Configuration
Using the patched release of the Web Deployment Console (WDC) on the IIS Web server, set the new per-authorized-Client setting for the Authorization Code flow with PKCE to enable or disable as required.
OAuth configuration (WDC patched settings) Authorization Code flow with PKCE = enable/disable per authorized Client - Configuration
Using the patched release of the Web Deployment Console (WDC) on the IIS Web server, set the new per-authorized-Client setting for the Resource Owner Password Credentials (ROPC) flow to enable or disable as required, especially if third-party web apps/services depend on ROPC.
OAuth configuration (WDC patched settings) Resource Owner Password Credentials (ROPC) flow = enable/disable per authorized Client - Compensating control
Locate control system networks and remote devices behind firewalls and isolate them from business networks.
- Compensating control
Minimize network exposure for all control system devices/systems and ensure they are not accessible from insecure networks.
- Compensating control
When remote access is required, use secure methods such as Virtual Private Networks (VPNs) and ensure VPNs are updated to the most current version available; recognize VPN security depends on connected devices.
- Operational
Verify the WDC patch is applied correctly by checking that the File version property of ./bin/Modules/WebDeployment/WebDeploymentConsole.exe matches the deployed release or later, and ensure any earlier release is no longer used.
- Operational
Verify the re-deployed Web Sites: ensure Web Sites have been redeployed as part of the remediation.
- Operational
If some HTTP security headers are not properly set by the web server, update IIS configuration manually for HTTP headers as part of the quick mitigation for missing headers.
- Operational
Uninstall the Web Server (as listed in the verification steps), then apply the updated IIS configuration/headers and re-deploy using the updated WDC.