Skip to main content

CVE-2026-32635

| EUVDEUVD-2026-12140 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-03-13 https://github.com/angular/angular GHSA-g93w-mfhg-p222
8.6
CVSS 4.0 · GitHub Advisory
Share

Severity by source

GitHub Advisory PRIMARY
8.6 HIGH
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Red Hat
6.3 MEDIUM
qualitative

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
P
Scope
X

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

DescriptionGitHub Advisory

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

AnalysisAI

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. With a CVSS score of 8.6 and no current evidence of active exploitation or public POCs, this represents a serious but not yet weaponized threat to Angular applications using i18n features with user-controlled data.

Technical ContextAI

Angular is a popular TypeScript-based web application framework developed by Google that includes built-in XSS protection through automatic sanitization of dangerous HTML attributes. The vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation) occurs specifically when developers combine Angular's internationalization features with data binding on security-sensitive attributes. When an attribute like href is marked with i18n-href for translation support, Angular's sanitization logic is bypassed, allowing unsanitized user input to be rendered directly into the DOM. The affected attributes include URL-based attributes (href, src, action, formaction), legacy HTML attributes (background, codebase, longdesc), and metadata attributes (cite, data, itemtype, poster, xlink:href) that browsers can interpret as executable contexts.

RemediationAI

Upgrade Angular to patched versions immediately: 19.2.20 or later for v19 users, 20.3.18 or later for v20 users, 21.2.4 or later for v21 users, or 22.0.0-next.3 or later for preview branch users. Until patching is complete, ensure no user-controlled data is bound to i18n-enabled sensitive attributes, or explicitly sanitize all such data using Angular's DomSanitizer service with the appropriate SecurityContext.URL context before binding. As a defense-in-depth measure, implement Content Security Policy (CSP) headers to restrict inline script execution and review all uses of i18n attributes on URL-accepting HTML attributes throughout your codebase.

Vendor StatusVendor

Share

CVE-2026-32635 vulnerability details – vuln.today

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