Web Application Scanning Engine Release 10.21
October ?? 2026
This release adds new detections for exposed client credentials and secret tokens, dependency confusion, and missing cross-origin security headers, extends custom signature diagnostics, and improves AI-assisted authentication status reporting and path-based testing accuracy.
New Feature
Dependency Confusion
What's New for You
You can now detect dependency confusion risks, reported under QID 531005, as the scan passively analyzes JavaScript bundles, HTML pages, JSON responses, and CSS files during the crawl phase to find internal or private package names exposed in your web content.
We have added detection for dependency confusion, reported under QID 531005.
A dependency confusion vulnerability occurs when an automatic package manager mistakenly downloads a malicious public software package instead of a legitimate private internal package with the exact same name. Most package managers are programmed to automatically fetch the highest version number available. If the public version is numbered higher, the system pulls the attacker's malicious code into the build or developer environment.
During a scan, the TAS engine passively analyzes HTTP response bodies (JavaScript bundles, HTML pages, JSON responses, and CSS files) in the crawl phase to detect internal or private npm-style package names that are exposed in web content. These findings are reported under QID 531005 as a potential vulnerability.
New Feature
Cross-Origin Security Headers
What's New for You
You can now see missing or misconfigured Cross-Origin-Resource-Policy, Cross-Origin-Opener-Policy, and Cross-Origin-Embedder-Policy headers reported as six new information gathering detections during the scan's crawl phase.
We have added six new information gathering (IG) detections for cross-origin security headers. Missing and misconfigured Cross-Origin-Resource-Policy (CORP), Cross-Origin-Opener-Policy (COOP), and Cross-Origin-Embedder-Policy (COEP) headers are tested during the crawl phase and reported under the informational security weakness category.
| QID | Detection |
|---|---|
| 531928 | Cross-Origin-Resource-Policy (CORP) header missing |
| 531929 | Cross-Origin-Resource-Policy (CORP) header misconfigured |
| 531930 | Cross-Origin-Opener-Policy (COOP) header missing |
| 531931 | Cross-Origin-Opener-Policy (COOP) header misconfigured |
| 531932 | Cross-Origin-Embedder-Policy (COEP) header missing |
| 531933 | Cross-Origin-Embedder-Policy (COEP) header misconfigured |
Cross-Origin-Resource-Policy (CORP) is a policy set by the Cross-Origin-Resource-Policy HTTP header that lets websites and applications opt in to protection against certain requests from other origins, such as those issued with elements like script and image tags. It mitigates speculative side-channel attacks, like Spectre, as well as cross-site script inclusion attacks. CORP is an additional layer of protection beyond the default same-origin policy. When the header is absent, the scan reports QID 531928. When the header is present but does not use one of the expected directives (same-site, same-origin, or cross-origin), the scan reports the misconfiguration under QID 531929.
Cross-Origin-Opener-Policy (COOP) is an HTTP response header that controls whether a top-level document shares a browsing context group with cross-origin windows, isolating the page to prevent side-channel and data leak attacks. The common directives are unsafe-none, same-origin-allow-popups, and same-origin. When the header is missing, the scan reports QID 531930. When the header is present but misconfigured, the scan reports QID 531931.
Cross-Origin-Embedder-Policy (COEP) is an HTTP response header that prevents a document from loading cross-origin resources unless those resources explicitly grant permission using CORP or CORS headers. The scan identifies links with a missing COEP header and reports them under QID 531932. The header should be set with just one token and an optional report-to endpoint. Setting the header more than once or with multiple tokens is equivalent to setting unsafe-none. The header has three main directives: unsafe-none, require-corp, and credentialless. If any of these are misconfigured, the scan reports QID 531933.
New Feature
Custom Signature Parsing and Error Reporting
What's New for You
You can now see custom signature parsing failures reported under QID 150619, along with the specific signature that could not be parsed, so you can confirm your custom signatures are valid and loaded successfully.
We have extended the custom signature diagnostics reported under QID 150619 to cover signature parsing failures and error responses.
When the scanner cannot parse a custom signature supplied in the scan configuration, the failure is now reported under QID 150619, along with the specific signature that could not be parsed. Use this diagnostic detection to confirm that your custom signatures are valid and were loaded successfully by the scan.
Enhancement
AI-Assisted Authentication Status Reporting
What Changed For You
You can now rely on AI-assisted authentication to report an authentication failure when your configured credentials are rejected, since the agent now confirms the login outcome on its own instead of requiring an explicit verification prompt.
We improved AI-assisted authentication to report the correct authentication status when incorrect or expired passwords are configured in a scan.
Previously, authentication could be reported as successful even when the application rejected the configured credentials, unless the optional prompt explicitly instructed the agent to verify that the login had succeeded. The agent now confirms the outcome of the login on its own, and the scan reports an authentication failure when the credentials are not accepted.
Enhancement
Path-Based Testing
What Changed For You
You can now get more accurate results from path-based testing, under QID 150004 and QID 150622, since the scanner confirms a tested path truly does not exist before flagging a finding, reducing false positives while still detecting legitimate vulnerabilities.
We improved path-based testing to avoid false positives while continuing to detect legitimate vulnerabilities. These improvements affect QID 150004 (Predictable Resource Location Via Forced Browsing) and QID 150622 (Suspected Path Manipulation Vulnerability).
Some applications return a 200 response code for URLs that do not exist, which could cause findings to be reported for paths that are not actually present. The scanner now sends an additional request to a sibling URL that is built by injecting a random token into the last path segment, so the URL is guaranteed not to exist. If the response for that URL matches the response for the mutated payload URL, the finding is filtered out as a false positive.
Qualys Notifications: Application Security Detections Published in September 2026