Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2amended

@angular/router: Denial of Service via RouterLink Query Parameter Retention in Server-Side Rendering (SSR)

CVE-2026-111751GHSA-57xq-rjx2-v5xh

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@angular/router 22.2.1, 21.2.25), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @angular/router

    Affected
    >= 22.0.0, < 22.2.1>= 21.2.0, < 21.2.25
    Fixed in
    22.2.1, 21.2.25

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.2 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

A denial of service (DoS) vulnerability was identified in @angular/router when Server-Side Rendering (SSR) is enabled on Node.js (V8) and RouterLink directives are rendered with queryParamsHandling: 'merge' or 'preserve', configured either per link or globally via defaultQueryParamsHandling. Starting in v21.2.0 (angular/angular#66181), RouterLink internals were refactored to use signals, introducing a computed signal (urlTree) that cached the returned UrlTree instance on the directive. Because each rendered link maintains an active RouterLink instance for the entire duration of the request lifecycle, the computed signal permanently pinned the UrlTree and its associated query parameter dictionary in the heap until the SSR response completed. When query parameter handling is set to 'merge' or 'preserve', each link copies the incoming request's query parameters into its own UrlTree. During SSR, memory consumption scales multiplicatively: $$\text{Heap Retention} \approx (\text{Number of…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-57xq-rjx2-v5xh

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-57xq-rjx2-v5xh

  4. Revision 1 · created ·

    Published from ghsa record GHSA-57xq-rjx2-v5xh

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-111751

Advisory: @angular/router: Denial of Service via RouterLink Query Parameter Retention in Server-Side Rendering (SSR)
IDs: CVE-2026-111751, GHSA-57xq-rjx2-v5xh
Record: https://patchnext.com/advisories/cve-2026-111751 (revision 4, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @angular/router 22.2.1, 21.2.25. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @angular/router: affected >= 22.0.0, < 22.2.1; >= 21.2.0, < 21.2.25; fixed in 22.2.1, 21.2.25

## Suggested inspection (read-only)
- `npm ls @angular/router --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @angular/router.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-57xq-rjx2-v5xh (GitHub-reviewed advisory GHSA-57xq-rjx2-v5xh lists affected ranges: npm @angular/router >=22.0.0 =21.2.0 <21.2.25)
- Verified: https://osv.dev/vulnerability/GHSA-57xq-rjx2-v5xh (OSV record GHSA-57xq-rjx2-v5xh lists affected ranges: npm @angular/router >=22.0.0 =21.2.0 <21.2.25 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…