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

HIGH
Advisory Identifier: GHSA-v3p8-whq6-r5jg
CWE-116 CWE-79
Published
Advisory Summary

CVE-2026-88060 is a HIGH cross-site scripting vulnerability (CWE-116: Improper Encoding or Escaping of Output) affecting Angular libraries in the npm ecosystem. The issue involves ssr xss via unescaped <template> content across documentfragment boundaries in fallback raw-content elements. Remediation is available by upgrading affected packages to version 22.1.4, 21.2.22, 20.3.30.

CVE-2026-88060 at a Glance

CVE Identifier CVE-2026-88060
GHSA Identifier GHSA-v3p8-whq6-r5jg
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-116: Improper Encoding or Escaping of Output
Affected Product Angular
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-88060

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/platform-server fixed: 22.1.4
npm install @angular/platform-server@22.1.4
@angular/platform-server fixed: 21.2.22
npm install @angular/platform-server@21.2.22
@angular/platform-server fixed: 20.3.30
npm install @angular/platform-server@20.3.30
@angular/platform-server fixed: Latest secure release
npm install @angular/platform-server@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/platform-server

How to Check if You Are Affected

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

npm ls @angular/platform-server

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 22.1.4), your application is affected.

Note: The npm ls @angular/platform-server 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-116: Improper Encoding or Escaping of Output, where the product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. as a result, the intended structure of the message is not preserved. 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

### Summary An XSS vulnerability exists in `@angular/platform-server` during server-side rendering (SSR) HTML serialization when traversing ancestor tags across `<template>` element boundaries. When an application renders untrusted user input within raw-text tags (`<xmp>`, `<style>`, `<script>`), comments, or text nodes inside a `<template>` that is nested within a fallback raw-content element (`<noscript>`, `<iframe>`, `<noembed>`, `<noframes>`), matching closing tags (e.g., `</noscript>`) are not escaped during HTML serialization. When rendered in a browser, this unescaped closing tag prematurely terminates the fallback container and executes trailing markup as active DOM elements. ### Technical Description In HTML5 parsing, fallback raw-content elements (`<noscript>`, `<iframe>`, `<noembed>`, `<noframes>`) place the browser's tokenizer into `RAWTEXT` mode. In this mode, inner content is parsed as literal text until an end tag matching the container tag name (e.g., `</noscript>`) is encountered. To prevent XSS breakout vectors during SSR serialization, the DOM serializer inspects a node's ancestors to escape any matching fallback closing tags (`</tag` -> `&lt;/tag`). However: 1. Per DOM specifications, the children of a `<template>` element reside in a separate `DocumentFragment` (`template.content`), whose own `parentNode` is `null`. 2. The serializer's ancestor traversal previously only inspected element nodes. When traversing upward from a node inside `template.content`, traversal terminated immediately at the `DocumentFragment` boundary. 3. Because traversal stopped before reaching the outer document tree, enclosing fallback raw-content ancestors (such as `<noscript>` or `<iframe>`) were not discovered. As a result, closing sequences like `</noscript>` within `<template>` content were emitted unescaped. ### Impact & Reachability * **Framework Guarantee Bypass**: Angular guarantees that standard text interpolation (`{{ userInput }}` bound as element text content) is safe by default without manual sanitization. This vulnerability bypasses that guarantee during SSR HTML serialization when untrusted input is interpolated inside template content within fallback containers. * **Template Authoring**: Writing literal `<xmp>` or `<style>` directly inside a component's `<template>` markup requires relaxed template schema checks (`CUSTOM_ELEMENTS_SCHEMA` or `NO_ERRORS_SCHEMA`). However, standard HTML comments and text nodes inside `<template>` within `<noscript>` are reachable without relaxed schemas. * **Imperative DOM Construction**: Components or directives that construct DOM structures imperatively via `Renderer2` bypass template compiler schema checks entirely and are unconditionally affected. ### Proof of Concept (Minimal Reproduction) ```ts import { Component } from '@angular/core'; @Component({ selector: 'app-root', standalone: true, template: ` <noscript> <template> <xmp>{{ payload }}</xmp> </template> </noscript> ` }) export class AppComponent { // Attacker-controlled input bound via standard text interpolation payload = '</noscript><img src=x onerror=alert("SSR_TEMPLATE_XSS")>'; } ``` **Vulnerable SSR Output**: ```html <noscript><template><xmp></noscript><img src=x onerror=alert("SSR_TEMPLATE_XSS")></xmp></template></noscript> ``` ### Workarounds * Avoid rendering untrusted user input inside `<template>` elements nested within `<noscript>`, `<iframe>`, `<noembed>`, or `<noframes>` in server-rendered templates. * Avoid programmatic DOM assembly of `<template>` elements inside fallback containers when handling untrusted data.

CVE-2026-88060 Affected Angular Versions

4 component(s)
Fixed Versions:
22.1.421.2.2220.3.30
Product / Package Ecosystem Affected Versions Fixed Version
@angular/platform-server
npm
≥ 22.0.0
< 22.1.4
22.1.4
@angular/platform-server
npm
≥ 21.0.0
< 21.2.22
21.2.22
@angular/platform-server
npm
≥ 20.0.0
< 20.3.30
20.3.30
@angular/platform-server
npm
≤ 19.2.25

References

Frequently Asked Questions

What is CVE-2026-88060?
CVE-2026-88060 is a security vulnerability in Angular involving SSR XSS via Unescaped <template> Content Across DocumentFragment Boundaries in Fallback Raw-Content Elements under CWE-116: Improper Encoding or Escaping of Output.
Which Angular versions are affected?
Affected versions include releases prior to 22.1.4, 21.2.22, 20.3.30 across affected packages: @angular/platform-server.
What version fixes CVE-2026-88060?
Upgrading to 22.1.4, 21.2.22, 20.3.30 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @angular/platform-server affected?
Yes, @angular/platform-server is affected in releases prior to 22.1.4, 21.2.22, 20.3.30, Latest secure release. Upgrade your dependency to 22.1.4, 21.2.22, 20.3.30, Latest secure release or later.
What CWE is associated with CVE-2026-88060?
CVE-2026-88060 is classified under CWE-116: Improper Encoding or Escaping of Output (The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.).
How can I check npm dependencies for CVE-2026-88060?
Run the dependency tree command: 'npm ls @angular/platform-server'. 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-v3p8-whq6-r5jg",
  "modified" : "2026-09-10T20:25:25Z",
  "published" : "2026-09-10T20:25:25Z",
  "aliases" : [ "CVE-2026-88060" ],
  "summary" : "Angular: SSR XSS via Unescaped <template> Content Across DocumentFragment Boundaries in Fallback Raw-Content Elements",
  "details" : "### Summary\nAn XSS vulnerability exists in `@angular/platform-server` during server-side rendering (SSR) HTML serialization when traversing ancestor tags across `<template>` element boundaries. When an application renders untrusted user input within raw-text tags (`<xmp>`, `<style>`, `<script>`), comments, or text nodes inside a `<template>` that is nested within a fallback raw-content element (`<noscript>`, `<iframe>`, `<noembed>`, `<noframes>`), matching closing tags (e.g., `</noscript>`) are not escaped during HTML serialization. When rendered in a browser, this unescaped closing tag prematurely terminates the fallback container and executes trailing markup as active DOM elements.\n\n### Technical Description\nIn HTML5 parsing, fallback raw-content elements (`<noscript>`, `<iframe>`, `<noembed>`, `<noframes>`) place the browser's tokenizer into `RAWTEXT` mode. In this mode, inner content is parsed as literal text until an end tag matching the container tag name (e.g., `</noscript>`) is encountered.\n\nTo prevent XSS breakout vectors during SSR serialization, the DOM serializer inspects a node's ancestors to escape any matching fallback closing tags (`</tag` -> `&lt;/tag`). However:\n1. Per DOM specifications, the children of a `<template>` element reside in a separate `DocumentFragment` (`template.content`), whose own `parentNode` is `null`.\n2. The serializer's ancestor traversal previously only inspected element nodes. When traversing upward from a node inside `template.content`, traversal terminated immediately at the `DocumentFragment` boundary.\n3. Because traversal stopped before reaching the outer document tree, enclosing fallback raw-content ancestors (such as `<noscript>` or `<iframe>`) were not discovered. As a result, closing sequences like `</noscript>` within `<template>` content were emitted unescaped.\n\n### Impact & Reachability\n* **Framework Guarantee Bypass**: Angular guarantees that standard text interpolation (`{{ userInput }}` bound as element text content) is safe by default without manual sanitization. This vulnerability bypasses that guarantee during SSR HTML serialization when untrusted input is interpolated inside template content within fallback containers.\n* **Template Authoring**: Writing literal `<xmp>` or `<style>` directly inside a component's `<template>` markup requires relaxed template schema checks (`CUSTOM_ELEMENTS_SCHEMA` or `NO_ERRORS_SCHEMA`). However, standard HTML comments and text nodes inside `<template>` within `<noscript>` are reachable without relaxed schemas.\n* **Imperative DOM Construction**: Components or directives that construct DOM structures imperatively via `Renderer2` bypass template compiler schema checks entirely and are unconditionally affected.\n\n### Proof of Concept (Minimal Reproduction)\n```ts\nimport { Component } from '@angular/core';\n\n@Component({\n  selector: 'app-root',\n  standalone: true,\n  template: `\n    <noscript>\n      <template>\n        <xmp>{{ payload }}</xmp>\n      </template>\n    </noscript>\n  `\n})\nexport class AppComponent {\n  // Attacker-controlled input bound via standard text interpolation\n  payload = '</noscript><img src=x onerror=alert(\"SSR_TEMPLATE_XSS\")>';\n}\n```\n**Vulnerable SSR Output**:\n```html\n<noscript><template><xmp></noscript><img src=x onerror=alert(\"SSR_TEMPLATE_XSS\")></xmp></template></noscript>\n```\n\n### Workarounds\n* Avoid rendering untrusted user input inside `<template>` elements nested within `<noscript>`, `<iframe>`, `<noembed>`, or `<noframes>` in server-rendered templates.\n* Avoid programmatic DOM assembly of `<template>` elements inside fallback containers when handling untrusted data.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/platform-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "22.0.0"
      }, {
        "fixed" : "22.1.4"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/platform-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "21.0.0"
      }, {
        "fixed" : "21.2.22"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/platform-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "20.0.0"
      }, {
        "fixed" : "20.3.30"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/platform-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "19.2.25"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/security/advisories/GHSA-v3p8-whq6-r5jg"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/commit/73d8bbd27cb46495426d4132975a1355b47ad915"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/commit/89b20568dfaee1ec8e0b3bcf1872acdddd2f4fef"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/commit/ba3bc47b20b3d12f5eb141ec9c651373ae4d15e8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/domino/commit/04f987dc08ff3736b427f50941adf1722458528f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/angular/angular"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/releases/tag/v20.3.30"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/releases/tag/v21.2.22"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/releases/tag/v22.1.4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-116", "CWE-79" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-10T20:25:25Z",
    "nvd_published_at" : null
  }
}