Vulnerability Database · npm · @angular/core · Version
@angular/core 21.2.8
21.2.8 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 0 Medium 2 Low 0 Unrated 0
-
Released 08 Apr 2026
Licence MIT
Also known from other sources 5
Newer releases 300
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
@angular/core 21.2.8 vulnerabilities
2 vulnerabilities cover @angular/core 21.2.8. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2026-50557: Angular Template and Attribute Namespace Sanitization Bypass (XSS) | 5.3 medium | 21.2.15 | 15 Jun 2026 |
| CVE-2026-52725: @angular/core Dynamic Component Namespace Bypass Leading to XSS | 5.3 medium | 21.2.15 | 15 Jun 2026 |
Looking for another version, or everything Vulert holds for @angular/core?
Questions
About @angular/core 21.2.8
Is @angular/core 21.2.8 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover @angular/core 21.2.8: 0 critical, 0 high, 2 medium and 0 low. Each entry above names the fixed version to move to.
Is 21.2.8 the latest release of @angular/core?
No. 21.2.8 was published 08 Apr 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor @angular/core for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @angular/core version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.