CVE-2026-32635

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

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.

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

• Fix 1
• Fix 2

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2026-32635 has a CVSS score of 9.0 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (22.0.0-next.3, 21.2.4, 20.3.18, 19.2.20); upgrading removes the vulnerable code path.

Kodem intelligence

• 22.0.0-next.3
• 21.2.4
• 20.3.18
• 19.2.20

1. What is CVE-2026-32635? CVE-2026-32635 is a high-severity cross-site scripting (XSS) vulnerability in @angular/core (npm), affecting versions >= 22.0.0-next.0, < 22.0.0-next.3. It is fixed in 22.0.0-next.3, 21.2.4, 20.3.18, 19.2.20. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2026-32635? CVE-2026-32635 has a CVSS score of 9.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-32635?
   • @angular/core (npm) (versions >= 22.0.0-next.0, < 22.0.0-next.3)
   • @angular/compiler (npm) (versions >= 22.0.0-next.0, < 22.0.0-next.3)
4. Is there a fix for CVE-2026-32635? Yes. CVE-2026-32635 is fixed in 22.0.0-next.3, 21.2.4, 20.3.18, 19.2.20. Upgrade to this version or later.
5. Is CVE-2026-32635 exploitable, and should I be worried? Whether CVE-2026-32635 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-32635 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-32635?
   • Upgrade @angular/core to 22.0.0-next.3 or later
   • Upgrade @angular/core to 21.2.4 or later
   • Upgrade @angular/core to 20.3.18 or later
   • Upgrade @angular/compiler to 22.0.0-next.3 or later
   • Upgrade @angular/compiler to 21.2.4 or later
   • Upgrade @angular/compiler to 20.3.18 or later
   • Upgrade @angular/core to 19.2.20 or later
   • Upgrade @angular/compiler to 19.2.20 or later