chore(deps): update dependency @angular/router to v22.2.0 [security] - #523
Merged
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
renovate
Bot
force-pushed
the
renovate/npm-angular-router-vulnerability
branch
10 times, most recently
from
October 4, 2026 13:07
bb2918c to
bbc6e97
Compare
renovate
Bot
force-pushed
the
renovate/npm-angular-router-vulnerability
branch
from
October 4, 2026 14:05
bbc6e97 to
137eae8
Compare
Brooooooklyn
approved these changes
Oct 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
22.1.7→22.2.0Angular Server-Side Rendering (SSR): Denial of Service via Numeric URL Matrix Parameters
CVE-2026-101896 / GHSA-ff3f-86qr-9cv3
More information
Details
A denial of service (DoS) vulnerability was identified in
@angular/routerwhen Server-Side Rendering (SSR) is enabled on Node.js (V8).When
@angular/routerparses incoming request URLs, it extracts path segments, matrix parameters, and child outlets into plain JavaScript objects (Record<string, string>). When matrix parameter names or outlet names are numeric strings (such as/a;990;2522), the V8 JavaScript engine interprets them as array-indexed properties rather than named properties.Under V8's internal property-storage heuristics, setting numeric keys on an initially empty object causes V8 to allocate a dense array backing store (
HOLEY_ELEMENTS) sized to the maximum index rather than falling back to sparse dictionary storage. Specifically, assigning sequential or moderately large numeric keys (like990followed by2522) causes V8 to allocate a contiguous backing store of ~2,522 pointers (~20 KB to 25 KB of heap) for a single 11-byte segment.Because each segment in a URL path allocates its own independent
parametersobject, an attacker can craft URLs with repeated numeric matrix parameters to achieve an asymmetric memory amplification factor of approximately ~350x.Impact
Successful exploitation allows an unauthenticated remote attacker to exhaust the Node.js old-space heap with modest request volume, terminating the SSR worker with an unrecoverable
JavaScript heap out of memoryfatal error and causing a Denial of Service./a;990;2522) consumes ~20 KB–25 KB of V8 heap.Attack Preconditions & Vulnerable Configurations
An application is affected only if all of the following conditions are met:
@angular/routerduring SSR.;) and multiple path segments without stripping or rejecting them.Exploit Payload Example
An attacker sends concurrent HTTP requests with repeated numeric matrix parameters:
Even with paths under 2 KB, overlapping requests during SSR will rapidly consume the V8 heap until the process crashes.
Patches
The issue is resolved by updating
@angular/routerto enforce V8 dictionary elements storage (setUrlDerivedKey) for numeric URL-derived keys (index >= 32). This prevents V8 from allocating oversized contiguous array backing stores while preserving route matching, parameter values, and component input bindings.22.2.021.2.2420.3.32Workarounds & Mitigations
If you cannot immediately upgrade to a patched version, apply one of the following mitigations at your edge or reverse proxy:
Configure your reverse proxy (e.g., Nginx, Cloudflare, or AWS WAF) to reject or strip semicolons (
;) in request paths before forwarding requests to the Angular SSR service:Reject requests with excessive path depth (e.g., more than 20–30 segments).
Increase
--max-old-space-size(e.g., to 2048 or 4096 MB) to increase the concurrency threshold required to exhaust memory, though this does not fully eliminate the vulnerability under sustained traffic.Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
angular/angular (@angular/router)
v22.2.0Compare Source
compiler
compiler-cli
core
Injectorfrom a view or content queryforms
readOnlyHintanduntrustedContentHintfor WebMCP implicit signal formslanguage-service
@boundaryblocks (#70463)router
v22.1.8Compare Source
common
compiler
compiler-cli
core
forms
platform-server
router
Configuration
📅 Schedule: (in timezone Asia/Shanghai)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.