# CVE-2026-27970: Angular i18n vulnerable to Cross-Site Scripting (XSS) > Attackers can execute arbitrary JavaScript in Angular applications by compromising translation files containing malicious ICU messages, leading to credential theft or page vandalism. - **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 26 Feb 2026 - **Updated:** 15 Jul 2026 - **Also known as:** CLSA-2026-1775176191, CLSA-2026-1775176192, CLSA-2026-1775781181, CLSA-2026-1776040411, CLSA-2026-1776040414, CLSA-2026-1776040417, CLSA-2026-1776126829, CLSA-2026-1776126831, CLSA-2026-1776126837, CLSA-2026-1776213249, CLSA-2026-1776299667, CLSA-2026-1776299671, CLSA-2026-1776386124, CLSA-2026-1792160917, CLSA-2026-1792160918, CLSA-2026-1792160981, CLSA-2026-1792161114, CLSA-2026-1792161117, CLSA-2026-1792161118, CLSA-2026-1792161119, CLSA-2026-1792161120, CLSA-2026-1792161121, CLSA-2026-1792161122, CLSA-2026-1792161123, CLSA-2026-1792161125, CLSA-2026-1792161126, CLSA-2026-1792161127, CLSA-2026-1792163502, CLSA-2026-1792163503, CLSA-2026-1792163506, CLSA-2026-1792163507, CLSA-2026-1792163508, CLSA-2026-1792163509, CLSA-2026-1792163510, CLSA-2026-1792163511, CLSA-2026-1792163512, CLSA-2026-1792163514, CLSA-2026-1792163515, CLSA-2026-1792163516, CLSA-2026-1792208089, CLSA-2026-1792208090, CLSA-2026-1792208091, CLSA-2026-1792208092, CLSA-2026-1792208093, CLSA-2026-1792208457, CLSA-2026-1792208504, CLSA-2026-1792208517, CLSA-2026-1792208528, CLSA-2026-1792208542, CLSA-2026-1792208543, CLSA-2026-1792208544, CLSA-2026-1792208572, CLSA-2026-1792250196, CLSA-2026-1792250197, CLSA-2026-1792250198, CLSA-2026-1792250199, CLSA-2026-1792250478, CLSA-2026-1792250524, CLSA-2026-1792250549, CLSA-2026-1792250565, CLSA-2026-1792250595, CLSA-2026-1792250596, CLSA-2026-1792250597, CLSA-2026-1792250598, CLSA-2026-1792250658, CLSA-2026-1792281042, CLSA-2026-1792281044, CLSA-2026-1792281045, CLSA-2026-1792281046, CLSA-2026-1792281047, CLSA-2026-1792281048, CLSA-2026-1792281049, CLSA-2026-1792281050, CLSA-2026-1792281051, CLSA-2026-1792281052, CLSA-2026-1792281710, CLSA-2026-1792281711, CLSA-2026-1792281805, CLSA-2026-1792325306, CLSA-2026-1792325308, CLSA-2026-1792325309, CLSA-2026-1792325310, CLSA-2026-1792325311, CLSA-2026-1792325312, CLSA-2026-1792325313, CLSA-2026-1792325932, CLSA-2026-1792325933, CLSA-2026-1792326026, CLSA-2026-1792326042, CLSA-2026-1792326051, CLSA-2026-1792326064, CLSA-2026-1792345166, CLSA-2026-1792345168, CLSA-2026-1792345169, CLSA-2026-1792345170, CLSA-2026-1792345171, CLSA-2026-1792345172, CLSA-2026-1792345173, CLSA-2026-1792345174, CLSA-2026-1792345175, CLSA-2026-1792345636, CLSA-2026-1792345637, CLSA-2026-1792345689, CLSA-2026-1792345723, CLSA-2026-1792357218, CLSA-2026-1792357219, CLSA-2026-1792357220, CLSA-2026-1792357221, CLSA-2026-1792357222, CLSA-2026-1792357223, CLSA-2026-1792357224, CLSA-2026-1792357225, CLSA-2026-1792357226, CLSA-2026-1792357771, CLSA-2026-1792358029, CLSA-2026-1792358064, CLSA-2026-1792366531, CLSA-2026-1792366532, CLSA-2026-1792366533, CLSA-2026-1792366534, CLSA-2026-1792366535, CLSA-2026-1792366880, CLSA-2026-1792366924, CLSA-2026-1792366940, CLSA-2026-1792366969, CLSA-2026-1792366970, CLSA-2026-1792366971, CLSA-2026-1792366972, CLSA-2026-1792367032, CLSA-2026-1792371589, CLSA-2026-1792371590, CLSA-2026-1792371591, CLSA-2026-1792371592, CLSA-2026-1792371593, CLSA-2026-1792372003, CLSA-2026-1792372053, CLSA-2026-1792372065, CLSA-2026-1792372070, CLSA-2026-1792375685, CLSA-2026-1792375686, CLSA-2026-1792375687, CLSA-2026-1792375688, CLSA-2026-1792375689, CLSA-2026-1792375690, CLSA-2026-1792375691, CLSA-2026-1792375692, CLSA-2026-1792376057, CLSA-2026-1792376075, CLSA-2026-1792376086, CLSA-2026-1792376097, CLSA-2026-1792376114, CLSA-2026-1792379946, CLSA-2026-1792379947, CLSA-2026-1792379948, CLSA-2026-1792379949, CLSA-2026-1792379950, CLSA-2026-1792380408, CLSA-2026-1792380409, CLSA-2026-1792380419, CLSA-2026-1792380430, CLSA-2026-1792380447, CLSA-2026-1792380474, CLSA-2026-1792380475, CLSA-2026-1792380476, CLSA-2026-1792382577, CLSA-2026-1792382578, CLSA-2026-1792382579, CLSA-2026-1792382580, CLSA-2026-1792382581, CLSA-2026-1792382582, CLSA-2026-1792382909, CLSA-2026-1792382925, CLSA-2026-1792382936, CLSA-2026-1792382946, CLSA-2026-1792382962, CLSA-2026-1792382993, CLSA-2026-1792383055, CLSA-2026-1792386051, CLSA-2026-1792386052, CLSA-2026-1792386053, CLSA-2026-1792386054, CLSA-2026-1792386055, CLSA-2026-1792386056, CLSA-2026-1792386057, CLSA-2026-1792386417, CLSA-2026-1792386440, CLSA-2026-1792386457, CLSA-2026-1792386468, CLSA-2026-1792386485, CLSA-2026-1792386513, CLSA-2026-1792500821, DEBIAN-CVE-2026-27970, GHSA-prjf-86w9-mfqv, UBUNTU-CVE-2026-27970 ## What is CVE-2026-27970? CVE-2026-27970 is a high-severity cross-site scripting vulnerability in angular, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official 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. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2026-27970? 10 open source packages ship an affected version, including @angular/core. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@angular/core` | npm | All versions to 18.2.14 | None | | `@angular/core` | npm | All versions to 18.2.14 | None | | `@angular/core` | npm | From 19.0.0-next.0 | 19.2.19 | | `@angular/core` | npm | From 19.0.0-next.0 | 19.2.19 | | `@angular/core` | npm | From 20.0.0-next.0 | 20.3.17 | | `@angular/core` | npm | From 20.0.0-next.0 | 20.3.17 | | `@angular/core` | npm | From 21.0.0-next.0 | 21.1.6 | | `@angular/core` | npm | From 21.0.0-next.0 | 21.1.6 | | `@angular/core` | npm | From 21.2.0-next.0 | 21.2.0 | | `@angular/core` | npm | From 21.2.0-next.0 | 21.2.0 | Products: Angular Angular. ## How do I fix CVE-2026-27970? Upgrade @angular/core to a fixed version for your release line: 19.2.19, 20.3.17, 21.1.6 or 21.2.0. ## Is CVE-2026-27970 being exploited? There is no known exploitation of CVE-2026-27970 in the wild and no public exploit code. ## Other vulnerabilities in angular - [CVE-2026-68945](https://insights.sbomify.com/CVE-2026-68945/): Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning (high 8.8) - [CVE-2026-46417](https://insights.sbomify.com/CVE-2026-46417/): Angular: SSRF via Hostname Hijacking in @angular/platform-server (high 8.8) - [CVE-2026-50168](https://insights.sbomify.com/CVE-2026-50168/): Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass (high 8.8) - [CVE-2026-54266](https://insights.sbomify.com/CVE-2026-54266/): Angular: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning (high 8.8) - [CVE-2026-41423](https://insights.sbomify.com/CVE-2026-41423/): Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-27970 and fix it if it is affected. What it is: CVE-2026-27970 is a high-severity cross-site scripting vulnerability in angular, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-27970 in the wild and no public exploit code. Affected packages and fixed versions: - @angular/core (npm): affected all versions up to 18.2.14; no fix listed - @angular/core (npm): affected all versions up to 18.2.14; no fix listed - @angular/core (npm): affected from 19.0.0-next.0; fixed in 19.2.19 - @angular/core (npm): affected from 19.0.0-next.0; fixed in 19.2.19 - @angular/core (npm): affected from 20.0.0-next.0; fixed in 20.3.17 - @angular/core (npm): affected from 20.0.0-next.0; fixed in 20.3.17 - @angular/core (npm): affected from 21.0.0-next.0; fixed in 21.1.6 - @angular/core (npm): affected from 21.0.0-next.0; fixed in 21.1.6 - @angular/core (npm): affected from 21.2.0-next.0; fixed in 21.2.0 - @angular/core (npm): affected from 21.2.0-next.0; fixed in 21.2.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-27970/ (Markdown: https://insights.sbomify.com/CVE-2026-27970/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27970 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27970 - OSV: https://osv.dev/vulnerability/CVE-2026-27970 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-27970/ Summaries are generated and may contain mistakes; the official description above is the record.