VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@angular/router: vulnerability history, versions and safety

@angular/router is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 36 releases, from Sep 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 20 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @angular/router vulnerabilities

Vulert verdict on @angular/router 22.2.3 i

Updated on 23 Oct 2026

Good news: 22.2.3, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Stay on 22.2.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 22.2.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 22.2.3 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 3 in the last year i
  • Latest disclosure 20 Oct 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Depended on by 211 packages i
  • Stars 101,110 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for @angular/router, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
22.2.3 14 Oct 2026 none MIT — Details →
22.3.0-next.2 14 Oct 2026 none MIT — Details →
20.3.34 14 Oct 2026 none MIT — Details →
22.3.0-next.1 08 Oct 2026 none MIT — Details →
22.2.2 08 Oct 2026 none MIT — Details →
22.3.0-next.0 30 Sep 2026 none MIT — Details →
22.2.1 30 Sep 2026 none MIT — Details →
21.2.25 30 Sep 2026 none MIT — Details →
20.3.33 30 Sep 2026 none MIT — Details →
22.2.0 23 Sep 2026 H2 MIT Yes Details →
21.2.24 23 Sep 2026 none MIT — Details →
20.3.32 23 Sep 2026 none MIT — Details →
22.1.8 23 Sep 2026 H3 MIT Yes Details →
22.2.0-rc.0 16 Sep 2026 H3 MIT Yes Details →
22.1.7 16 Sep 2026 H3 MIT Yes Details →
22.2.0-next.7 09 Sep 2026 H3 MIT Yes Details →
22.2.0-next.6 09 Sep 2026 H3 MIT Yes Details →
22.1.6 09 Sep 2026 H3 MIT Yes Details →
20.3.31 09 Sep 2026 none MIT — Details →
21.2.23 09 Sep 2026 none MIT — Details →
22.2.0-next.5 03 Sep 2026 H3 MIT Yes Details →
22.1.5 03 Sep 2026 H3 MIT Yes Details →
22.2.0-next.4 27 Aug 2026 H3 MIT Yes Details →
22.1.4 27 Aug 2026 H3 MIT Yes Details →
21.2.22 26 Aug 2026 none MIT — Details →
20.3.30 26 Aug 2026 none MIT — Details →
22.2.0-next.3 19 Aug 2026 H3 MIT Yes Details →
22.1.3 19 Aug 2026 H3 MIT Yes Details →
20.3.29 19 Aug 2026 none MIT — Details →
21.2.21 19 Aug 2026 none MIT — Details →
22.1.2 13 Aug 2026 H3 MIT Yes Details →
22.2.0-next.2 13 Aug 2026 H3 MIT Yes Details →
20.3.28 13 Aug 2026 none MIT — Details →
21.2.20 13 Aug 2026 none MIT — Details →
22.2.0-next.1 07 Aug 2026 H3 MIT Yes Details →
22.1.1 07 Aug 2026 H3 MIT Yes Details →
22.2.0-next.0 29 Jul 2026 H3 MIT Yes Details →
21.2.19 29 Jul 2026 none MIT — Details →
22.1.0 29 Jul 2026 H3 MIT Yes Details →
20.3.27 29 Jul 2026 none MIT — Details →
22.1.0-rc.0 22 Jul 2026 H3 MIT Yes Details →
22.0.8 22 Jul 2026 H3 MIT Yes Details →
22.1.0-next.6 16 Jul 2026 H3 MIT Yes Details →
22.0.7 16 Jul 2026 H3 MIT Yes Details →
20.3.26 08 Jul 2026 none MIT — Details →
21.2.18 08 Jul 2026 none MIT — Details →
22.1.0-next.5 08 Jul 2026 H3 MIT Yes Details →
22.0.6 08 Jul 2026 H3 MIT Yes Details →
22.1.0-next.4 01 Jul 2026 H3 MIT Yes Details →
22.0.5 01 Jul 2026 H3 MIT Yes Details →
22.1.0-next.3 26 Jun 2026 H3 MIT Yes Details →
22.0.4 26 Jun 2026 H3 MIT Yes Details →
22.1.0-next.2 25 Jun 2026 H3 MIT Yes Details →
22.0.3 25 Jun 2026 H3 MIT Yes Details →
22.1.0-next.1 17 Jun 2026 H3 MIT Yes Details →
22.0.2 17 Jun 2026 H3 MIT Yes Details →
22.1.0-next.0 10 Jun 2026 H3 MIT Yes Details →
22.0.1 10 Jun 2026 H3 MIT Yes Details →
21.2.17 10 Jun 2026 none MIT — Details →
20.3.25 10 Jun 2026 none MIT — Details →
22.0.0 03 Jun 2026 H3 MIT Yes Details →
21.2.16 03 Jun 2026 none MIT — Details →
19.2.25 02 Jun 2026 none MIT — Details →
20.3.24 02 Jun 2026 none MIT — Details →
22.0.0-rc.3 01 Jun 2026 none MIT — Details →
22.0.0-rc.2 28 May 2026 none MIT — Details →
21.2.15 28 May 2026 none MIT — Details →
19.2.24 28 May 2026 none MIT — Details →
20.3.23 28 May 2026 none MIT — Details →
20.3.22 27 May 2026 none MIT — Details →
19.2.23 27 May 2026 none MIT — Details →
22.0.0-rc.1 20 May 2026 none MIT — Details →
21.2.14 20 May 2026 none MIT — Details →
22.0.0-rc.0 13 May 2026 none MIT — Details →
21.2.13 13 May 2026 none MIT — Details →
19.2.22 12 May 2026 none MIT — Details →
20.3.21 12 May 2026 none MIT — Details →
22.0.0-next.12 08 May 2026 none MIT — Details →
22.0.0-next.11 06 May 2026 none MIT — Details →
21.2.12 06 May 2026 none MIT — Details →
20.3.20 06 May 2026 none MIT — Details →
22.0.0-next.10 29 Apr 2026 none MIT — Details →
21.2.11 29 Apr 2026 none MIT — Details →
22.0.0-next.9 22 Apr 2026 none MIT — Details →
21.2.10 22 Apr 2026 none MIT — Details →
19.2.21 15 Apr 2026 none MIT — Details →
20.3.19 15 Apr 2026 none MIT — Details →
22.0.0-next.8 15 Apr 2026 none MIT — Details →
21.2.9 15 Apr 2026 none MIT — Details →
22.0.0-next.7 08 Apr 2026 none MIT — Details →
21.2.8 08 Apr 2026 none MIT — Details →
22.0.0-next.6 01 Apr 2026 none MIT — Details →
21.2.7 01 Apr 2026 none MIT — Details →
22.0.0-next.5 25 Mar 2026 none MIT — Details →
21.2.6 25 Mar 2026 none MIT — Details →
22.0.0-next.4 19 Mar 2026 none MIT — Details →
21.2.5 18 Mar 2026 none MIT — Details →
19.2.20 12 Mar 2026 none MIT — Details →
20.3.18 12 Mar 2026 none MIT — Details →
22.0.0-next.3 12 Mar 2026 none MIT — Details →
21.2.4 12 Mar 2026 none — — Details →
22.0.0-next.2 11 Mar 2026 none — — Details →
21.2.3 11 Mar 2026 none — — Details →
21.2.2 09 Mar 2026 none — — Details →
22.0.0-next.1 05 Mar 2026 none — — Details →
22.0.0-next.0 04 Mar 2026 none — — Details →
21.2.1 04 Mar 2026 none — — Details →
19.2.19 25 Feb 2026 none — — Details →
20.3.17 25 Feb 2026 none — — Details →
21.2.0 25 Feb 2026 none — — Details →
21.1.6 25 Feb 2026 none — — Details →
21.2.0-rc.0 18 Feb 2026 none — — Details →
21.1.5 18 Feb 2026 none — — Details →
21.2.0-next.3 11 Feb 2026 none — — Details →
21.1.4 11 Feb 2026 none — — Details →
21.2.0-next.2 05 Feb 2026 none — — Details →
21.1.3 05 Feb 2026 none — — Details →
21.2.0-next.1 28 Jan 2026 none — — Details →
21.1.2 28 Jan 2026 none — — Details →
21.2.0-next.0 22 Jan 2026 none — — Details →

The newest 120 of 1,138 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @angular/router

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2026-101896: @angular/router Denial of Service via Numeric URL Matrix Parameters 8.2 high 22.2.0 30 Sep 2026
CVE-2026-111752: @angular/router Denial of Service via Unmatched Empty-Path Outlet Route Matching 8.2 high 22.2.1 20 Oct 2026
CVE-2026-111751: @angular/router Denial of Service via RouterLink Query Parameter Retention in SSR 8.2 high 22.2.1 20 Oct 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @angular/router

Is @angular/router safe to use?

Vulert records 3 vulnerabilities for @angular/router in npm: 0 critical, 3 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @angular/router's Vulert package health score?

Vulert scores @angular/router 84/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @angular/router affected?

No. 22.2.3, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does @angular/router have?

3 vulnerabilities are recorded for @angular/router in the npm ecosystem: 0 critical, 3 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @angular/router vulnerabilities disclosed?

3 vulnerabilities were recorded for @angular/router in the last 12 months, and the oldest entry in this database dates to 30 Sep 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @angular/router are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @angular/router for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @angular/router version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.