Angular is a widely used npm package. As of 2026-05-24, there are 14 known vulnerabilities in the OSV database. The latest stable version is 1.8.3. Developers should audit their dependency trees and update to patched versions.
Package Overview
Known Vulnerabilities (14)
| ID | Severity | Score | Affected Versions | Fixed In | Description |
|---|---|---|---|---|---|
| CVE-2024-21490 | HIGH | 7.5 | >= 1.3.0; >= 1.3.0; >= 1.3.0 | N/A | angular vulnerable to super-linear runtime due to backtracking |
| CVE-2019-10768 | HIGH | 7.5 | 0 to 1.7.9 | 1.7.9 | angular Prototype Pollution vulnerability |
| GHSA-28hp-fgcr-2r4h | MODERATE | 5.0 | 0 to 1.6.0 | 1.6.0 | Cross-Site Scripting via JSONP |
| CVE-2023-26117 | MODERATE | 5.0 | >= 0 | N/A | angular vulnerable to regular expression denial of service via the $resource service |
| CVE-2023-26116 | MODERATE | 5.0 | >= 0 | N/A | angular vulnerable to regular expression denial of service via the angular.copy() utility |
| GHSA-5cp4-xmrw-59wf | MODERATE | 5.0 | 0 to 1.8.0 | 1.8.0 | XSS via JQLite DOM manipulation functions in AngularJS |
| CVE-2022-25844 | MODERATE | 5.0 | >= 1.7.0 | N/A | angular vulnerable to regular expression denial of service (ReDoS) |
| CVE-2020-7676 | MODERATE | 5.0 | 0 to 1.8.0 | 1.8.0 | Angular vulnerable to Cross-site Scripting |
| CVE-2022-25869 | MODERATE | 5.0 | >= 0 | N/A | Angular (deprecated package) Cross-site Scripting |
| CVE-2023-26118 | MODERATE | 5.0 | >= 0 | N/A | angular vulnerable to regular expression denial of service via the <input type="url"> element |
| CVE-2019-14863 | MODERATE | 5.0 | 0 to 1.5.0-beta.1 | 1.5.0-beta.1 | AngularJS Cross-site Scripting due to failure to sanitize `xlink.href` attributes |
| CVE-2025-0716 | LOW | 2.5 | >= 0 | N/A | AngularJS improperly sanitizes SVG elements |
| CVE-2024-8372 | LOW | 2.5 | >= 1.3.0-rc.4 | N/A | AngularJS allows attackers to bypass common image source restrictions |
| CVE-2024-8373 | LOW | 2.5 | >= 0 | N/A | AngularJS allows attackers to bypass common image source restrictions |
Security Recommendations
- Pin Angular to the latest stable version (1.8.3) in your dependency manifest
- Enable automated dependency updates with Dependabot or Renovate
- Run regular vulnerability scans using
npm audit - Review your lock file (.package-lock.json) after every update
- Monitor the OSV database and NIST NVD for new advisories
FAQ
Is Angular safe to use?
Angular is actively maintained and widely used. As of 2026-05-24, there are 14 known vulnerabilities listed in the OSV database. Most have patches available. Keeping your dependencies updated and running regular security audits significantly reduces risk.
What vulnerabilities does Angular have?
The OSV database currently lists 14 vulnerabilities for Angular. These range in severity and are detailed in the vulnerability table above. Check the linked advisories for full technical details and remediation guidance.
How do I update Angular to fix vulnerabilities?
Run npm update angular or npm install angular@latest to get the newest version. Use npm audit to identify vulnerable dependencies in your project. Enable automated updates with Dependabot or Renovate to stay current.
Using AI-Generated Code with Angular?
Our vibe coding security audit checks for misconfigurations, exposed secrets and vulnerable dependencies in AI-generated codebases. If your project uses Angular, we can verify it is locked to a safe version and properly configured.
Get a Vibe Coding Security Audit