Skip to content
OpenAdvisories

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Versions prior to 21.2.0, 21.1.16, 20.3.17, and 19.2.19 have a cross-Site scripting vulnerability in the Angular internationalization (i18n) pipeline. In ICU messages (International Components for Unicode), HTML from translated content was not properly sanitized and could execute arbitrary JavaScript. Angular i18n typically involves three steps, extracting all messages from an application in the source language, sending the messages to be translated, and then merging their translations back into the final source code. Translations are frequently handled by contracts with specific partner companies, and involve sending the source messages to a separate contractor before receiving final translations for display to the end user. If the returned translations have malicious content, it could be rendered into the application and execute arbitrary JavaScript. When successfully exploited, this vulnerability allows for execution of attacker controlled JavaScript in the application origin. Depending on the nature of the application being exploited this could lead to credential exfiltration and/or page vandalism. Several preconditions apply to the attack. The attacker must compromise the translation file (xliff, xtb, etc.). Unlike most XSS vulnerabilities, this issue is not exploitable by arbitrary users. An attacker must first compromise an application's translation file before they can escalate privileges into the Angular application client. The victim application must use Angular i18n, use one or more ICU messages, render an ICU message, and not defend against XSS via a safe content security policy. Versions 21.2.0, 21.1.6, 20.3.17, and 19.2.19 patch the issue. Until the patch is applied, developers should consider reviewing and verifying translated content received from untrusted third parties before incorporating it in an Angular application, enabling strict CSP controls to block unauthorized JavaScript from executing on the page, and enabling Trusted Types to enforce proper HTML sanitization.

Affected products

VendorProductAffectedFixed
angular angular >= 21.2.0-next.0, < 21.2.0, >= 21.0.0-next.0, < 21.1.6, >= 20.0.0-next.0, < 20.3.17, >= 19.0.0-next.0, < 19.2.19, <= 18.2.14 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 13 angular.js No fix yet —
Debian 12 angular.js No fix yet —
ReleasePackageFixed inAdvisory
Ubuntu 26.10 angular.js No fix yet —
Ubuntu 26.04 LTS angular.js No fix yet —
Ubuntu 25.10 angular.js No fix yet —
Ubuntu 24.04 LTS angular.js No fix yet —
Ubuntu 22.04 LTS angular.js No fix yet —
Show 3 more (older releases, extended support, other products)
ReleasePackageFixed inAdvisory
Ubuntu Pro 20.04 LTS angular.js No fix yet —
Ubuntu Pro 18.04 LTS angular.js No fix yet —
Ubuntu Pro 16.04 LTS angular.js No fix yet —

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling katib-earlystopping +8 0.19.0-r31 —
Wolfi rolling katib-suggestion-goptuna-compat 0.19.0-r40 —

Affected packages

EcosystemPackageAffectedFixedRecord
npm @angular/core >= 21.2.0-next.0, < 21.2.0 21.2.0 GHSA-prjf-86w9-mfqv
npm @angular/core >= 21.0.0-next.0, < 21.1.6 21.1.6 GHSA-prjf-86w9-mfqv
npm @angular/core >= 20.0.0-next.0, < 20.3.17 20.3.17 GHSA-prjf-86w9-mfqv
npm @angular/core >= 19.0.0-next.0, < 19.2.19 19.2.19 GHSA-prjf-86w9-mfqv
npm @angular/core <= 18.2.14 — GHSA-prjf-86w9-mfqv

Advisories 1

References