CVE-2026-32635

Overview

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-next.3, 21.2.4, 20.3.18, and 19.2.20, 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. This vulnerability is fixed in 22.0.0-next.3, 21.2.4, 20.3.18, and 19.2.20.

‍

Details

Module Info

• Product: Angular
• Affected packages: @angular/core
• Affected versions: >= 22.0.0-next.0, < 22.0.0-next.3, >= 21.0.0-next.0, < 21.2.4, >= 20.0.0-next.0.0.0, < 20.3.18, >= 19.0.0.next.0, < 19.2.20, >= 17.0.0.next.0, <= 18.2.14
• GitHub repository: https://github.com/angular/angular
• Package manager: Maven
• Fixed In: Angular NES v22.0.0-next.3

Vulnerability Info

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:

<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:

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) || '';
 }
}



Mitigation

• Update your project to one of the following patched versions:
  
• Audit i18n Bindings: Search your templates for the i18n- prefix used on security-sensitive attributes (e.g., i18n-href, i18n-src).
• Manual Sanitization: If an immediate upgrade is not possible, use Angular's DomSanitizer to manually validate untrusted strings before binding.