EUVD-2026-12140

| CVE-2026-32635 HIGH
2026-03-13 https://github.com/angular/angular GHSA-g93w-mfhg-p222
8.6
CVSS 4.0
Share

CVSS Vector

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
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
P

Lifecycle Timeline

5
PoC Detected
Mar 16, 2026 - 14:53 vuln.today
Public exploit code
Patch Released
Mar 16, 2026 - 14:53 nvd
Patch available
EUVD ID Assigned
Mar 13, 2026 - 21:01 euvd
EUVD-2026-12140
Analysis Generated
Mar 13, 2026 - 21:01 vuln.today
CVE Published
Mar 13, 2026 - 20:56 nvd
HIGH 8.6

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

Analysis

A Cross-Site Scripting (XSS) vulnerability in Angular's runtime and compiler allows attackers to bypass built-in sanitization when internationalization (i18n) is enabled on security-sensitive attributes like href, src, and action. The vulnerability affects Angular versions before 19.2.20, 20.3.18, 21.2.4, and 22.0.0-next.3, enabling attackers with low privileges to execute arbitrary JavaScript in users' browsers for session hijacking, data theft, and unauthorized actions. …

Sign in for full analysis, threat intelligence, and remediation guidance.

Remediation

Within 24 hours: Identify all applications using Angular and determine which leverage i18n attributes on href, src, action, or similar security-sensitive attributes. Within 7 days: Apply the available Angular patch to all affected applications and conduct regression testing. …

Sign in for detailed remediation steps.

Priority Score

63
Low Medium High Critical
KEV: 0
EPSS: +0.0
CVSS: +43
POC: +20

Share

EUVD-2026-12140 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy