Incomplete Filtering of Special Elements Affecting angular package, versions >=1.2.0
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Incomplete Filtering of Special Elements vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-ANGULAR-17458840
- published25 Jun 2026
- disclosed24 Jun 2026
- creditGeorge Kalpakas
Introduced: 24 Jun 2026
NewCVE-2026-11998 (opens in a new tab)How to fix?
There is no fixed version for angular.
Overview
angular is a package that lets you write client-side web applications as if you had a smarter browser. It also lets you use HTML as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly.
Affected versions of this package are vulnerable to Incomplete Filtering of Special Elements in the $sceDelegate service's trustedResourceUrlList() validation, where a regular expression intended to match the entire resource URL is only partially applied when the pattern contains an alternation operator. An attacker can execute JavaScript in a victim's browser by supplying a resource URL such as https://evil.com/scripts.js#https://good.com/ that satisfies the partially applied pattern and bypasses the Strict Contextual Escaping allowlist. Exploitation is possible only where the application configures trustedResourceUrlList() with regex matchers that use alternation (|).