Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
8.6
Angular: Malicious Code Can Be Injected Through Sensitive Attributes
GHSA-g93w-mfhg-p222
CVE-2026-32635
GHSA-g93w-mfhg-p222
Summary
A security issue has been found in Angular that allows hackers to inject malicious code into your website by exploiting certain attributes. This could allow them to steal user data, hijack sessions, or take unauthorized actions within your application. To fix this, update to the latest version of Angular and ensure that you're not using attributes like href, action, or src with user-generated data.
What to do
- Update angular core to version 22.0.0-next.3.
- Update angular core to version 21.2.4.
- Update angular core to version 20.3.18.
- Update angular core to version 19.2.20.
- Update angular compiler to version 22.0.0-next.3.
- Update angular compiler to version 21.2.4.
- Update angular compiler to version 20.3.18.
- Update angular compiler to version 19.2.20.
- Update angular @angular/core to version 22.0.0-next.3.
- Update angular @angular/core to version 21.2.4.
- Update angular @angular/core to version 20.3.18.
- Update angular @angular/core to version 19.2.20.
- Update angular @angular/compiler to version 22.0.0-next.3.
- Update angular @angular/compiler to version 21.2.4.
- Update angular @angular/compiler to version 20.3.18.
- Update angular @angular/compiler to version 19.2.20.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| angular | core | > 22.0.0-next.0 , <= 22.0.0-next.3 | 22.0.0-next.3 |
| angular | core | > 21.0.0-next.0 , <= 21.2.4 | 21.2.4 |
| angular | core | > 20.0.0-next.0.0.0 , <= 20.3.18 | 20.3.18 |
| angular | core | > 19.0.0.next.0 , <= 19.2.20 | 19.2.20 |
| angular | core | > 17.0.0.next.0 , <= 18.2.14 | – |
| angular | compiler | > 22.0.0-next.0 , <= 22.0.0-next.3 | 22.0.0-next.3 |
| angular | compiler | > 21.0.0-next.0 , <= 21.2.4 | 21.2.4 |
| angular | compiler | > 20.0.0-next.0.0.0 , <= 20.3.18 | 20.3.18 |
| angular | compiler | > 19.0.0.next.0 , <= 19.2.20 | 19.2.20 |
| angular | compiler | > 17.0.0.next.0 , <= 18.2.14 | – |
| angular | @angular/core | > 22.0.0-next.0 , <= 22.0.0-next.3 | 22.0.0-next.3 |
| angular | @angular/core | > 21.0.0-next.0 , <= 21.2.4 | 21.2.4 |
| angular | @angular/core | > 20.0.0-next.0.0.0 , <= 20.3.18 | 20.3.18 |
| angular | @angular/core | > 19.0.0.next.0 , <= 19.2.20 | 19.2.20 |
| angular | @angular/core | > 17.0.0.next.0 , <= 18.2.14 | – |
| angular | @angular/compiler | > 22.0.0-next.0 , <= 22.0.0-next.3 | 22.0.0-next.3 |
| angular | @angular/compiler | > 21.0.0-next.0 , <= 21.2.4 | 21.2.4 |
| angular | @angular/compiler | > 20.0.0-next.0.0.0 , <= 20.3.18 | 20.3.18 |
| angular | @angular/compiler | > 19.0.0.next.0 , <= 19.2.20 | 19.2.20 |
| angular | @angular/compiler | > 17.0.0.next.0 , <= 18.2.14 | – |
Original title
Angular vulnerable to XSS in i18n attribute bindings
Original description
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) || '';
}
}
```
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) || '';
}
}
```
ghsa CVSS4.0
8.6
Vulnerability type
CWE-79
Cross-site Scripting (XSS)
- 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/224e60ecb1b90115baa702f1c06edc1d64d861...
- https://github.com/angular/angular/commit/78dea55351fb305b33a919c43a6b363137eca1...
- https://github.com/angular/angular/commit/8630319f74c9575a21693d875cc7d525251614...
- https://github.com/angular/angular/commit/ed2d324f9cc12aab6cfa0569ef10b73243a62c...
- https://github.com/advisories/GHSA-g93w-mfhg-p222
- https://github.com/angular/angular Product
Published: 13 Mar 2026 · Updated: 14 Mar 2026 · First seen: 13 Mar 2026