npm package report

Is @angular/ssr safe?

5 known vulnerabilities, worst severity CRITICAL.

cvss
9.2

how bad it is if exploited, out of 10

epss
0.50%

chance of exploitation in the next 30 days

xyz score
4.6

CyberXYZ composite, out of 10

fig. 01 — GHSA-x288-3778-4hhx, the advisory selected below

// advisories

GHSA-x288-3778-4hhx

CRITICALCVE-2026-27739

A [Server-Side Request Forgery (SSRF)](https://developer.mozilla.org/en-US/docs/Web/Security/Attacks/SSRF) vulnerability has been identified in the Angular SSR request handling pipeline. The vulnerability exists because Angular’s internal URL reconstruction logic directly trusts and consumes user-controlled HTTP headers specifically the Host and X-Forwarded- family to determine the application's b

Affected
>= 21.2.0-next.0, < 21.2.0-rc.0
Fixed in
21.2.0-rc.1
Weakness
CWE-918
Published
2026-02-25
Source
github

GHSANVDMITREreferencereferencereferencereference

// dependencies

1 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 02:50 UTC. The most recent advisory here was published 2026-05-06. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @angular/ssr safe? npm package security report | CyberXYZ