VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@angular/ssr: vulnerability history, versions and safety

@angular/ssr is a package in the npm ecosystem. Vulert records 6 vulnerabilities for it across 31 releases, from Oct 2025 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
6 vulnerabilities recorded C1 H1 M4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
5 in the last 12 months

Most recent disclosure 05 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @angular/ssr vulnerabilities

Vulert verdict on @angular/ssr 22.2.4 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 22.2.4 — unaffected i
  • Vulnerabilities on record 6 over 1 year · 5 in the last year i
  • Latest disclosure 05 Oct 2026 i
  • Highest CVSS 9.2 i
  • With no published fix 0 i
  • Stars 27,014 i
  • OpenSSF scorecard 6/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/ssr, 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.4 22 Oct 2026 none MIT — Details →
22.3.0-next.2 15 Oct 2026 none MIT — Details →
22.2.3 15 Oct 2026 none MIT — Details →
21.2.27 15 Oct 2026 none MIT — Details →
20.3.40 14 Oct 2026 none MIT — Details →
22.3.0-next.1 07 Oct 2026 none MIT — Details →
22.2.2 07 Oct 2026 none MIT — Details →
21.2.26 07 Oct 2026 none MIT — Details →
20.3.39 07 Oct 2026 none MIT — Details →
21.2.25 05 Oct 2026 none MIT — Details →
20.3.38 05 Oct 2026 none MIT — Details →
22.3.0-next.0 01 Oct 2026 none MIT — Details →
22.2.1 01 Oct 2026 none MIT — Details →
22.2.0 23 Sep 2026 none MIT — Details →
22.1.9 23 Sep 2026 none MIT — Details →
22.2.0-rc.0 16 Sep 2026 none MIT — Details →
22.2.0-next.7 10 Sep 2026 none MIT — Details →
21.2.24 10 Sep 2026 none MIT — Details →
20.3.37 10 Sep 2026 none MIT — Details →
22.1.8 10 Sep 2026 none MIT — Details →
22.2.0-next.6 02 Sep 2026 none MIT — Details →
22.1.7 02 Sep 2026 none MIT — Details →
21.2.23 02 Sep 2026 none MIT — Details →
20.3.36 02 Sep 2026 none MIT — Details →
22.2.0-next.5 26 Aug 2026 none MIT — Details →
22.1.6 26 Aug 2026 M1 MIT Yes Details →
21.2.22 26 Aug 2026 none MIT — Details →
20.3.35 26 Aug 2026 none MIT — Details →
22.2.0-next.4 19 Aug 2026 none MIT — Details →
22.1.5 19 Aug 2026 M1 MIT Yes Details →
22.2.0-next.3 13 Aug 2026 none MIT — Details →
22.1.4 13 Aug 2026 M1 MIT Yes Details →
21.2.21 12 Aug 2026 none MIT — Details →
20.3.34 12 Aug 2026 none MIT — Details →
22.2.0-next.2 05 Aug 2026 none MIT — Details →
22.2.0-next.1 05 Aug 2026 none MIT — Details →
22.1.3 05 Aug 2026 M1 MIT Yes Details →
21.2.20 05 Aug 2026 none MIT — Details →
20.3.33 05 Aug 2026 none MIT — Details →
22.1.2 30 Jul 2026 M1 MIT Yes Details →
22.1.1 30 Jul 2026 M1 MIT Yes Details →
22.2.0-next.0 30 Jul 2026 none MIT — Details →
22.1.0 29 Jul 2026 M1 MIT Yes Details →
22.0.9 29 Jul 2026 M1 MIT Yes Details →
22.1.0-rc.0 23 Jul 2026 M1 MIT Yes Details →
22.0.8 23 Jul 2026 M1 MIT Yes Details →
22.1.0-next.4 15 Jul 2026 M1 MIT Yes Details →
22.0.7 15 Jul 2026 M1 MIT Yes Details →
21.2.19 09 Jul 2026 none MIT — Details →
20.3.32 09 Jul 2026 none MIT — Details →
22.1.0-next.3 09 Jul 2026 M1 MIT Yes Details →
22.0.6 09 Jul 2026 M1 MIT Yes Details →
22.1.0-next.2 01 Jul 2026 M1 MIT Yes Details →
22.0.5 01 Jul 2026 M1 MIT Yes Details →
21.2.18 01 Jul 2026 none MIT — Details →
20.3.31 01 Jul 2026 none MIT — Details →
22.1.0-next.1 24 Jun 2026 M1 MIT Yes Details →
22.0.4 24 Jun 2026 M1 MIT Yes Details →
21.2.17 24 Jun 2026 none MIT — Details →
20.3.30 24 Jun 2026 none MIT — Details →
22.0.3 18 Jun 2026 M1 MIT Yes Details →
21.2.16 17 Jun 2026 none MIT — Details →
20.3.29 17 Jun 2026 none MIT — Details →
22.0.2 17 Jun 2026 M1 MIT Yes Details →
22.1.0-next.0 11 Jun 2026 M1 MIT Yes Details →
20.3.28 11 Jun 2026 none MIT — Details →
21.2.15 11 Jun 2026 none MIT — Details →
22.0.1 10 Jun 2026 M1 MIT Yes Details →
22.0.0 03 Jun 2026 M1 MIT Yes Details →
21.2.14 03 Jun 2026 none MIT — Details →
20.3.27 02 Jun 2026 none MIT — Details →
19.2.27 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.13 27 May 2026 none MIT — Details →
22.0.0-rc.1 21 May 2026 none MIT — Details →
21.2.12 20 May 2026 none MIT — Details →
22.0.0-rc.0 13 May 2026 none MIT — Details →
21.2.11 13 May 2026 none MIT — Details →
20.3.26 13 May 2026 none MIT — Details →
19.2.26 13 May 2026 none MIT — Details →
22.0.0-next.8 11 May 2026 none MIT — Details →
21.2.10 06 May 2026 none MIT — Details →
19.2.25 30 Apr 2026 none MIT — Details →
22.0.0-next.7 29 Apr 2026 none MIT — Details →
20.3.25 29 Apr 2026 none MIT — Details →
21.2.9 29 Apr 2026 none MIT — Details →
22.0.0-next.6 22 Apr 2026 M1 MIT Yes Details →
21.2.8 22 Apr 2026 none MIT — Details →
20.3.24 15 Apr 2026 none MIT — Details →
20.3.23 08 Apr 2026 none MIT — Details →
19.2.24 08 Apr 2026 none MIT — Details →
22.0.0-next.5 08 Apr 2026 M1 MIT Yes Details →
21.2.7 08 Apr 2026 none MIT — Details →
22.0.0-next.4 01 Apr 2026 M1 MIT Yes Details →
21.2.6 01 Apr 2026 none MIT — Details →
21.2.5 27 Mar 2026 none MIT — Details →
20.3.22 27 Mar 2026 none MIT — Details →
19.2.23 27 Mar 2026 none MIT — Details →
22.0.0-next.3 26 Mar 2026 M1 MIT Yes Details →
21.2.4 26 Mar 2026 none — — Details →
20.3.21 19 Mar 2026 none — — Details →
22.0.0-next.2 18 Mar 2026 M1 — Yes Details →
21.2.3 18 Mar 2026 none — — Details →
22.0.0-next.1 11 Mar 2026 M2 — Yes Details →
21.2.2 11 Mar 2026 none — — Details →
20.3.20 11 Mar 2026 none — — Details →
22.0.0-next.0 05 Mar 2026 M2 — Yes Details →
21.2.1 05 Mar 2026 none — — Details →
20.3.19 04 Mar 2026 none — — Details →
20.3.18 26 Feb 2026 none — — Details →
19.2.22 26 Feb 2026 none — — Details →
21.2.0 25 Feb 2026 none — — Details →
21.2.0-rc.2 24 Feb 2026 none — — Details →
21.2.0-rc.1 23 Feb 2026 none — — Details →
21.1.5 23 Feb 2026 none — — Details →
20.3.17 23 Feb 2026 none — — Details →
19.2.21 23 Feb 2026 none — — Details →
21.2.0-rc.0 18 Feb 2026 C1 M1 — Yes Details →
19.2.20 13 Feb 2026 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 5

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

03 Vulnerabilities

Recorded vulnerabilities for @angular/ssr

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-27739: Angular SSR Vulnerable to SSRF and Header Injection 9.2 critical 21.2.0-rc.1 25 Feb 2026
CVE-2025-62427: SSRF Vulnerability in @angular/ssr Package 8.7 high 19.2.18 16 Oct 2025
CVE-2026-27738: Open Redirect Vulnerability in @angular/ssr 6.9 medium 21.2.0-rc.1 25 Feb 2026
CVE-2026-33397: @angular/ssr Protocol-Relative URL Injection Vulnerability 6.9 medium 22.0.0-next.2 19 Mar 2026
CVE-2026-44437: Angular SSR Open Redirect and Request Steering via Encoded X-Forwarded-Prefix 6.9 medium 22.0.0-next.7 06 May 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/ssr

Is @angular/ssr safe to use?

Vulert records 6 vulnerabilities for @angular/ssr in npm: 1 critical, 1 high, 4 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/ssr's Vulert package health score?

Vulert scores @angular/ssr 79/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/ssr affected?

No. 22.2.4, 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/ssr have?

6 vulnerabilities are recorded for @angular/ssr in the npm ecosystem: 1 critical, 1 high, 4 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/ssr vulnerabilities disclosed?

5 vulnerabilities were recorded for @angular/ssr in the last 12 months, and the oldest entry in this database dates to 16 Oct 2025. 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/ssr 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/ssr for upcoming vulnerabilities?

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