CVE-2026-32635: @angular/core Cross-Site Scripting Vulnerability

HIGH
Advisory Identifier: GHSA-g93w-mfhg-p222
CVSS 9.0
CWE-79
Published
Advisory Summary

CVE-2026-32635 is a HIGH (CVSS 9.0) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting @angular/core libraries in the npm ecosystem. The issue involves angular vulnerable to xss in i18n attribute bindings. Remediation is available by upgrading affected packages to version 22.0.0-next.3, 21.2.4, 20.3.18, 19.2.20.

CVE-2026-32635 at a Glance

CVE Identifier CVE-2026-32635
GHSA Identifier GHSA-g93w-mfhg-p222
Severity HIGH
CVSS v3.1 Base Score 9.0
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product @angular/core
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 9.0

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

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

How to Fix CVE-2026-32635

To remediate this vulnerability, upgrade all affected @angular/core 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/core fixed: 22.0.0-next.3
npm install @angular/core@22.0.0-next.3
@angular/core fixed: 21.2.4
npm install @angular/core@21.2.4
@angular/core fixed: 20.3.18
npm install @angular/core@20.3.18
@angular/core fixed: 19.2.20
npm install @angular/core@19.2.20
@angular/core fixed: Latest secure release
npm install @angular/core@Latest secure release
@angular/compiler fixed: 22.0.0-next.3
npm install @angular/compiler@22.0.0-next.3
@angular/compiler fixed: 21.2.4
npm install @angular/compiler@21.2.4
@angular/compiler fixed: 20.3.18
npm install @angular/compiler@20.3.18
@angular/compiler fixed: 19.2.20
npm install @angular/compiler@19.2.20
@angular/compiler fixed: Latest secure release
npm install @angular/compiler@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/core

How to Check if You Are Affected

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

npm ls @angular/core

Analyze the terminal output to locate any version of @angular/core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 22.0.0-next.3), your application is affected.

Note: The npm ls @angular/core 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-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In @angular/core, 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 Cross-Site Scripting (XSS) vulnerability has been identified in the Angular runtime and compiler. It occurs when the application uses a security-sensitive attribute (for example href on an anchor tag) together with Angular's ability to internationalize attributes. Enabling internationalization for the sensitive attribute by adding `i18n-<attribute>` name bypasses Angular's built-in sanitization mechanism, which when combined with a data binding to untrusted user-generated data can allow an attacker to inject a malicious script. The following example illustrates the issue: ```html <a href="{{maliciousUrl}}" i18n-href>Click me</a> ``` The following attributes have been confirmed to be vulnerable: - `action` - `background` - `cite` - `codebase` - `data` - `formaction` - `href` - `itemtype` - `longdesc` - `poster` - `src` - `xlink:href` ### Impact When exploited, this vulnerability allows an attacker to execute arbitrary code within the context of the vulnerable application's domain. This enables: - Session Hijacking: Stealing session cookies and authentication tokens. - Data Exfiltration: Capturing and transmitting sensitive user data. - Unauthorized Actions: Performing actions on behalf of the user. ### Attack Preconditions 1. The application must use a vulnerable version of Angular. 2. The application must bind unsanitized user input to one of the attributes mentioned above. 3. The bound value must be marked for internationalization via the presence of a `i18n-<name>` attribute on the same element. ### Patches - 22.0.0-next.3 - 21.2.4 - 20.3.18 - 19.2.20 ### Workarounds The primary workaround is to ensure that any data bound to the vulnerable attributes is **never sourced from untrusted user input** (e.g., database, API response, URL parameters) until the patch is applied, or when it is, it shouldn't be marked for internationalization. Alternatively, users can explicitly sanitize their attributes by passing them through Angular's `DomSanitizer`: ```ts import {Component, inject, SecurityContext} from '@angular/core'; import {DomSanitizer} from '@angular/platform-browser'; @Component({ template: ` <form action="{{url}}" i18n-action> <button>Submit</button> </form> `, }) export class App { url: string; constructor() { const dangerousUrl = 'javascript:alert(1)'; const sanitizer = inject(DomSanitizer); this.url = sanitizer.sanitize(SecurityContext.URL, dangerousUrl) || ''; } } ``` ### References - [Fix 1](https://github.com/angular/angular/pull/67541) - [Fix 2](https://github.com/angular/angular/pull/67561)

CVE-2026-32635 Affected @angular/core Versions

10 component(s)
Fixed Versions:
22.0.0-next.321.2.420.3.1819.2.20
Product / Package Ecosystem Affected Versions Fixed Version
@angular/core
npm
≥ 22.0.0-next.0
< 22.0.0-next.3
22.0.0-next.3
@angular/core
npm
≥ 21.0.0-next.0
< 21.2.4
21.2.4
@angular/core
npm
≥ 20.0.0-next.0.0.0
< 20.3.18
20.3.18
@angular/core
npm
≥ 19.0.0-next.0
< 19.2.20
19.2.20
@angular/core
npm
≥ 17.0.0-next.0
≤ 18.2.14
@angular/compiler
npm
≥ 22.0.0-next.0
< 22.0.0-next.3
22.0.0-next.3
@angular/compiler
npm
≥ 21.0.0-next.0
< 21.2.4
21.2.4
@angular/compiler
npm
≥ 20.0.0-next.0.0.0
< 20.3.18
20.3.18
@angular/compiler
npm
≥ 19.0.0-next.0
< 19.2.20
19.2.20
@angular/compiler
npm
≥ 17.0.0-next.0
≤ 18.2.14

References

Frequently Asked Questions

What is CVE-2026-32635?
CVE-2026-32635 is a security vulnerability in @angular/core involving Angular vulnerable to XSS in i18n attribute bindings under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which @angular/core versions are affected?
Affected versions include releases prior to 22.0.0-next.3, 21.2.4, 20.3.18, 19.2.20 across affected packages: @angular/core, @angular/compiler.
What version fixes CVE-2026-32635?
Upgrading to 22.0.0-next.3, 21.2.4, 20.3.18, 19.2.20 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @angular/core affected?
Yes, @angular/core is affected in releases prior to 22.0.0-next.3, 21.2.4, 20.3.18, 19.2.20, Latest secure release. Upgrade your dependency to 22.0.0-next.3, 21.2.4, 20.3.18, 19.2.20, Latest secure release or later.
Is @angular/compiler affected?
Yes, @angular/compiler is affected in releases prior to 22.0.0-next.3, 21.2.4, 20.3.18, 19.2.20, Latest secure release. Upgrade your dependency to 22.0.0-next.3, 21.2.4, 20.3.18, 19.2.20, Latest secure release or later.
What is the CVSS score of CVE-2026-32635?
CVE-2026-32635 has a CVSS v3.1 base score of 9.0 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2026-32635?
CVE-2026-32635 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check npm dependencies for CVE-2026-32635?
Run the dependency tree command: 'npm ls @angular/core'. 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-g93w-mfhg-p222",
  "modified" : "2026-05-06T20:33:10Z",
  "published" : "2026-03-13T20:56:18Z",
  "aliases" : [ "CVE-2026-32635" ],
  "summary" : "Angular vulnerable to XSS in i18n attribute bindings",
  "details" : "A Cross-Site Scripting (XSS) vulnerability has been identified in the Angular runtime and compiler. It occurs when the application uses a security-sensitive attribute (for example href on an anchor tag) together with Angular's ability to internationalize attributes. Enabling internationalization for the sensitive attribute by adding `i18n-<attribute>` name bypasses Angular's built-in sanitization mechanism, which when combined with a data binding to untrusted user-generated data can allow an attacker to inject a malicious script. \n\nThe following example illustrates the issue:\n```html\n<a href=\"{{maliciousUrl}}\" i18n-href>Click me</a>\n```\n\nThe following attributes have been confirmed to be vulnerable:\n- `action`\n- `background`\n- `cite`\n- `codebase`\n- `data`\n- `formaction`\n- `href`\n- `itemtype`\n- `longdesc`\n- `poster`\n- `src`\n- `xlink:href`\n\n### Impact\nWhen exploited, this vulnerability allows an attacker to execute arbitrary code within the context of the vulnerable application's domain. This enables:\n- Session Hijacking: Stealing session cookies and authentication tokens.\n- Data Exfiltration: Capturing and transmitting sensitive user data.\n- Unauthorized Actions: Performing actions on behalf of the user.\n\n### Attack Preconditions\n1. The application must use a vulnerable version of Angular.\n2. The application must bind unsanitized user input to one of the attributes mentioned above.\n3. The bound value must be marked for internationalization via the presence of a `i18n-<name>` attribute on the same element.\n\n### Patches\n- 22.0.0-next.3\n- 21.2.4\n- 20.3.18\n- 19.2.20\n\n### Workarounds\nThe primary workaround is to ensure that any data bound to the vulnerable attributes is **never sourced from untrusted user input** (e.g., database, API response, URL parameters) until the patch is applied, or when it is, it shouldn't be marked for internationalization.\n\nAlternatively, users can explicitly sanitize their attributes by passing them through Angular's `DomSanitizer`:\n```ts\nimport {Component, inject, SecurityContext} from '@angular/core';\nimport {DomSanitizer} from '@angular/platform-browser';\n\n@Component({\n  template: `\n    <form action=\"{{url}}\" i18n-action>\n      <button>Submit</button>\n    </form>\n  `,\n})\nexport class App {\n  url: string;\n\n  constructor() {\n    const dangerousUrl = 'javascript:alert(1)';\n    const sanitizer = inject(DomSanitizer);\n    this.url = sanitizer.sanitize(SecurityContext.URL, dangerousUrl) || '';\n  }\n}\n```\n\n### References\n- [Fix 1](https://github.com/angular/angular/pull/67541) \n- [Fix 2](https://github.com/angular/angular/pull/67561)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "22.0.0-next.0"
      }, {
        "fixed" : "22.0.0-next.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "21.0.0-next.0"
      }, {
        "fixed" : "21.2.4"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "20.0.0-next.0.0.0"
      }, {
        "fixed" : "20.3.18"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "19.0.0-next.0"
      }, {
        "fixed" : "19.2.20"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "17.0.0-next.0"
      }, {
        "last_affected" : "18.2.14"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/compiler"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "22.0.0-next.0"
      }, {
        "fixed" : "22.0.0-next.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/compiler"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "21.0.0-next.0"
      }, {
        "fixed" : "21.2.4"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/compiler"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "20.0.0-next.0.0.0"
      }, {
        "fixed" : "20.3.18"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/compiler"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "19.0.0-next.0"
      }, {
        "fixed" : "19.2.20"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/compiler"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "17.0.0-next.0"
      }, {
        "last_affected" : "18.2.14"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/security/advisories/GHSA-g93w-mfhg-p222"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-32635"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/pull/67541"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/pull/67561"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/commit/224e60ecb1b90115baa702f1c06edc1d64d86187"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/commit/78dea55351fb305b33a919c43a6b363137eca166"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/commit/8630319f74c9575a21693d875cc7d5252516146d"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/commit/ed2d324f9cc12aab6cfa0569ef10b73243a62c65"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/angular/angular"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-13T20:56:18Z",
    "nvd_published_at" : "2026-03-16T14:19:40Z"
  }
}