Answer in brief
CVE-2026-27970 records a High severity (CVSS 6.1) vulnerability in Angular i18n vulnerable to Cross-Site Scripting (XSS). The current sources do not mark it as known exploited. The current feed maps angular/angular (generic), @angular/core (npm), @angular/core (npm), @angular/core (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps angular/angular (generic), @angular/core (npm), @angular/core (npm), @angular/core (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| angular/angulargeneric | >=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 | 21.2.0, 21.1.6, 20.3.17, 19.2.19 |
| @angular/corenpm | >=21.2.0-next.0,<=21.2.0-rc.0 | 21.2.0 |
| @angular/corenpm | >=21.0.0-next.0,<=21.1.5 | 21.1.6 |
| @angular/corenpm | >=20.0.0-next.0,<=20.3.16 | 20.3.17 |
| @angular/corenpm | >=19.0.0-next.0,<=19.2.18 | 19.2.19 |
| @angular/corenpm | <=18.2.14 | Not reported |
| @angular/corenpm | >=21.2.0-next.0,<=21.2.0-rc.0 | 21.2.0 |
| @angular/corenpm | >=21.0.0-next.0,<=21.1.5 | 21.1.6 |
| @angular/corenpm | >=20.0.0-next.0,<=20.3.16 | 20.3.17 |
| @angular/corenpm | >=19.0.0-next.0,<=19.2.18 | 19.2.19 |
| @angular/corenpm | <=18.2.14 | Not reported |
Published upstream
Feb 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.