CVE-2026-32635: Angular vulnerable to XSS in i18n attribute bindings
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.
Published Mar 13, 2026 · Updated May 6, 2026
Affected packages
@angular/core
- Ecosystem
- npm
- Affected
- >= 22.0.0-next.0, < 22.0.0-next.3
- Fixed in
- 22.0.0-next.3
- Check
npm ls @angular/core
@angular/core
- Ecosystem
- npm
- Affected
- >= 21.0.0-next.0, < 21.2.4
- Fixed in
- 21.2.4
- Check
npm ls @angular/core
@angular/core
- Ecosystem
- npm
- Affected
- >= 20.0.0-next.0.0.0, < 20.3.18
- Fixed in
- 20.3.18
- Check
npm ls @angular/core
@angular/compiler
- Ecosystem
- npm
- Affected
- >= 22.0.0-next.0, < 22.0.0-next.3
- Fixed in
- 22.0.0-next.3
- Check
npm ls @angular/compiler
@angular/compiler
- Ecosystem
- npm
- Affected
- >= 21.0.0-next.0, < 21.2.4
- Fixed in
- 21.2.4
- Check
npm ls @angular/compiler
@angular/compiler
- Ecosystem
- npm
- Affected
- >= 20.0.0-next.0.0.0, < 20.3.18
- Fixed in
- 20.3.18
- Check
npm ls @angular/compiler
@angular/core
- Ecosystem
- npm
- Affected
- >= 19.0.0-next.0, < 19.2.20
- Fixed in
- 19.2.20
- Check
npm ls @angular/core
@angular/core
- Ecosystem
- npm
- Affected
- >= 17.0.0-next.0, <= 18.2.14
- Fixed in
- No patched version yet
- Check
npm ls @angular/core
@angular/compiler
- Ecosystem
- npm
- Affected
- >= 19.0.0-next.0, < 19.2.20
- Fixed in
- 19.2.20
- Check
npm ls @angular/compiler
@angular/compiler
- Ecosystem
- npm
- Affected
- >= 17.0.0-next.0, <= 18.2.14
- Fixed in
- No patched version yet
- Check
npm ls @angular/compiler
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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:
Click meThe following attributes have been confirmed to be vulnerable:
actionbackgroundcitecodebasedataformactionhrefitemtypelongdescpostersrcxlink: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
- The application must use a vulnerable version of Angular.
- The application must bind unsanitized user input to one of the attributes mentioned above.
- 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) || '';
}
}References
Credited to alan-agius4, AndrewKushnir, securityMB, josephperrott, crisbeto, hdtmccallie, VenkatKwest.
References
- https://github.com/angular/angular/security/advisories/GHSA-g93w-mfhg-p222
- https://github.com/angular/angular/pull/67541
- https://github.com/angular/angular/pull/67561
- https://github.com/angular/angular/commit/224e60ecb1b90115baa702f1c06edc1d64d86187
- https://github.com/angular/angular/commit/78dea55351fb305b33a919c43a6b363137eca166
- https://github.com/angular/angular/commit/8630319f74c9575a21693d875cc7d5252516146d
- https://github.com/angular/angular/commit/ed2d324f9cc12aab6cfa0569ef10b73243a62c65
- https://nvd.nist.gov/vuln/detail/CVE-2026-32635
- https://github.com/advisories/GHSA-g93w-mfhg-p222
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-88057
Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler
medium5.3No fixSep 10, 2026CVE-2026-69151
Angular i18n: Cross-Site Scripting (XSS) via event-handler attributes
high7.6No fixAug 3, 2026CVE-2026-50557
Angular: Template and Attribute Namespace Sanitization Bypass (XSS)
medium6.1No fixJun 15, 2026CVE-2026-52725
@angular/core: Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS)
medium6.1No fixJun 15, 2026CVE-2026-54265
@angular/compiler: Two-Way Property Binding Sanitization Bypass (XSS)
medium6.1No fixJun 15, 2026CVE-2026-54267
Angular Client Hydration DOM Clobbering & Response-Cache Poisoning
high6.1No fixJun 15, 2026
