fix(deps): update dependency @angular/platform-server to v20.3.0 [security] #433
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:
20.1.6
->20.3.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
CVE-2025-59052
Impact
Angular uses a DI container (the "platform injector") to hold request-specific state during server-side rendering. For historical reasons, the container was stored as a JavaScript module-scoped global variable. When multiple requests are processed concurrently, they could inadvertently share or overwrite the global injector state.
In practical terms, this can lead to one request responding with data meant for a completely different request, leaking data or tokens included on the rendered page or in response headers. As long as an attacker had network access to send any traffic that received a rendered response, they may have been able to send a large number of requests and then inspect the responses for information leaks.
The following APIs were vulnerable and required SSR-only breaking changes:
bootstrapApplication
: This function previously implicitly retrieved the last platform injector that was created. It now requires an explicitBootstrapContext
in a server environment. This function is only used for standalone applications. NgModule-based applications are not affected.getPlatform
: This function previously returned the last platform instance that was created. It now always returnsnull
in a server environment.destroyPlatform
: This function previously destroyed the last platform instance that was created. It's now a no-op when called in a server environment.For
bootstrapApplication
, the framework now provides a new argument to the application's bootstrap function:As is usually the case for changes to Angular, an automatic schematic will take care of these code changes as part of ng update:
The schematic can also be invoked explicitly if the version bump was pulled in independently:
For applications that still use
CommonEngine
, thebootstrap
property inCommonEngineOptions
also gains the samecontext
argument in the patched versions of Angular.In local development (
ng serve
), Angular CLI triggered a codepath for Angular's "JIT" feature on the server even in applications that weren't using it in the browser. The codepath introduced async behavior between platform creation and application bootstrap, triggering the race condition even if an application didn't explicitly usegetPlatform
or custom async logic inbootstrap
. Angular applications should never run in this mode outside of local development.Patches
The issue has been patched in all active release lines as well as in the v21 prerelease:
@angular/platform-server
: 21.0.0-next.3@angular/platform-server
: 20.3.0@angular/platform-server
: 19.2.15@angular/platform-server:
18.2.14@angular/ssr
: 21.0.0-next.3@angular/ssr
: 20.3.0@angular/ssr
: 19.2.16@angular/ssr
: 18.2.21Workarounds
bootstrap
functions.getPlatform()
in application code.ngJitMode
as false.References
Release Notes
angular/angular (@angular/platform-server)
v20.3.0
Compare Source
Breaking Changes
core
The server-side bootstrapping process has been changed to eliminate the reliance on a global platform injector.
Before:
After:
A schematic is provided to automatically update
main.server.ts
files to pass theBootstrapContext
to thebootstrapApplication
call.In addition,
getPlatform()
anddestroyPlatform()
will now returnnull
and be a no-op respectively when running in a server environment.(cherry picked from commit
8bf80c9
)core
BootstrapContext
for improved server bootstrapping (#63636)v20.2.4
Compare Source
core
platform-server
v20.2.3
Compare Source
compiler
core
rxResource
stream
threw before returning anObservable
(#63342)v20.2.2
Compare Source
compiler
core
@for
loop animations never get cancelled (#63328)animate.leave
binding to a string with spaces (#63366)v20.2.1
Compare Source
compiler
v20.2.0
Compare Source
Deprecations
animations
core
router
animations
compiler
compiler-cli
core
as
aliases onelse if
blocks (#63047)animate.enter
class removal when composing classes (#62981)@if
toggles with leave animations (#63048)forms
http
HttpClient
(#62586)language-service
platform-browser
router
currentNavigation
signal to theRouter
service. (#62971)service-worker
v20.1.8
Compare Source
compiler
compiler-cli
v20.1.7
Compare Source
compiler
compiler-cli
core
afterRenderEffect
(#63001)router
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.