CVE-2026-11998: Angular Cross-Site Scripting Vulnerability

HIGH
Advisory Identifier: GHSA-7x27-g8rg-x87w
CVSS 7.6
CWE-791 CWE-79
Published
Advisory Summary

CVE-2026-11998 is a HIGH (CVSS 7.6) cross-site scripting vulnerability (CWE-791: Incomplete Filtering of Special Elements) affecting Angular libraries in the npm ecosystem. The issue involves angular's deprecated package has a cross-site scripting issue. Remediation is available in the latest vendor maintenance releases.

CVE-2026-11998 at a Glance

CVE Identifier CVE-2026-11998
GHSA Identifier GHSA-7x27-g8rg-x87w
Severity HIGH
CVSS v3.1 Base Score 7.6
CWE Classification CWE-791: Incomplete Filtering of Special Elements
Affected Product Angular
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.6

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability Low (A:L)

How to Fix CVE-2026-11998

To remediate this vulnerability, upgrade all affected Angular dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

angular fixed: Latest secure release
npm install angular@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls angular

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-11998, inspect your project dependencies using npm:

npm ls angular

Analyze the terminal output to locate any version of Angular in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The npm ls angular command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-791: Incomplete Filtering of Special Elements, where the product receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component. In Angular, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

A flaw in AngularJS' Strict Contextual Escaping (SCE) logic allows bypassing certain SCE policies for resource URLs and can lead to arbitrary JavaScript execution within the context of the victim's browser session. SCE's purpose is to ensure that only trusted or safe values are used in certain security-sensitive contexts, such as resource URLs, including URLs that define executable JavaScript scripts, '<iframe>' documents, route templates, etc. A flaw in the logic that tries to match entire URLs against regular expression matchers can result in partial matches for certain types of regular expressions, effectively bypassing the policies and allowing the use of unsafe values as resource URLs. This issue affects AngularJS versions greater than or equal to 1.2.0-rc.3. Note: The AngularJS project was already End-of-Life when this CVE was published and will not receive any updates to address this issue. For more information see the  End-of-Life announcement https://docs.angularjs.org/misc/version-support-status .

CVE-2026-11998 Affected Angular Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
angular
npm
≥ 1.2.0-rc.3
≤ 1.8.3

References

Frequently Asked Questions

What is CVE-2026-11998?
CVE-2026-11998 is a security vulnerability in Angular involving Angular's deprecated package has a Cross-Site Scripting issue under CWE-791: Incomplete Filtering of Special Elements.
Which Angular versions are affected?
Affected versions include releases prior to current release patches across affected packages: angular.
What version fixes CVE-2026-11998?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is angular affected?
Yes, angular is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-11998?
CVE-2026-11998 has a CVSS v3.1 base score of 7.6 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L.
What CWE is associated with CVE-2026-11998?
CVE-2026-11998 is classified under CWE-791: Incomplete Filtering of Special Elements (The product receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component.).
How can I check npm dependencies for CVE-2026-11998?
Run the dependency tree command: 'npm ls angular'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-7x27-g8rg-x87w",
  "modified" : "2026-07-17T21:47:01Z",
  "published" : "2026-06-24T21:30:44Z",
  "aliases" : [ "CVE-2026-11998" ],
  "summary" : "Angular's deprecated package has a Cross-Site Scripting issue",
  "details" : "A flaw in AngularJS' Strict Contextual Escaping (SCE) logic allows bypassing certain SCE policies for resource URLs and can lead to arbitrary JavaScript execution within the context of the victim's browser session.\n\n\nSCE's purpose is to ensure that only trusted or safe values are used in certain security-sensitive contexts, such as resource URLs, including URLs that define executable JavaScript scripts, '<iframe>' documents, route templates, etc. A flaw in the logic that tries to match entire URLs against regular expression matchers can result in partial matches for certain types of regular expressions, effectively bypassing the policies and allowing the use of unsafe values as resource URLs.\n\n\nThis issue affects AngularJS versions greater than or equal to 1.2.0-rc.3.\n\n\nNote:\nThe AngularJS project was already End-of-Life when this CVE was published and will not receive any updates to address this issue. For more information see the  End-of-Life announcement https://docs.angularjs.org/misc/version-support-status .",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "angular"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.2.0-rc.3"
      }, {
        "last_affected" : "1.8.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-11998"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/security/cve/CVE-2026-11998"
  }, {
    "type" : "WEB",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2492579"
  }, {
    "type" : "WEB",
    "url" : "https://codepen.io/herodevs/pen/JobQdmz/5b3896f56fab66f20cd25e698cf3faa8"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/angular/angular.js"
  }, {
    "type" : "WEB",
    "url" : "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-11998.json"
  }, {
    "type" : "WEB",
    "url" : "https://www.herodevs.com/vulnerability-directory/cve-2026-11998"
  }, {
    "type" : "WEB",
    "url" : "https://www.herodevs.com/vulnerability-directory/cve-2026-11998?nes-for-angularjs"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79", "CWE-791" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-17T21:47:00Z",
    "nvd_published_at" : "2026-06-24T21:16:52Z"
  }
}