fix(deps): update dependency @angular/ssr to v18 [security] #28
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:
^17.0.2→^18.0.0GitHub 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 explicitBootstrapContextin 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 returnsnullin 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, thebootstrapproperty inCommonEngineOptionsalso gains the samecontextargument 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 usegetPlatformor 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
bootstrapfunctions.getPlatform()in application code.ngJitModeas false.References
Release Notes
angular/angular-cli (@angular/ssr)
v18.2.21Compare Source
Breaking Changes
@angular/ssr
The server-side bootstrapping process has been changed to eliminate the reliance on a global platform injector.
Before:
After:
@angular-devkit/build-angular
@angular/build
@angular/ssr
v18.2.20Compare Source
@angular-devkit/build-angular
v18.2.19Compare Source
@angular-devkit/build-angular
v18.2.18Compare Source
@angular/build
v18.2.17Compare Source
@angular/build
v18.2.16Compare Source
@angular-devkit/build-angular
@vitejs/plugin-basic-sslfrom dependencies@angular/build
v18.2.15Compare Source
@angular-devkit/build-angular
v18.2.14Compare Source
@angular-devkit/build-angular
vitedependencyv18.2.13Compare Source
@angular/cli
ng add@angular/build
v18.2.12Compare Source
@angular/cli
@angular/build
v18.2.11Compare Source
@angular/build
v18.2.10Compare Source
@angular-devkit/build-angular
http-proxy-middlewareto3.0.3@angular/build
v18.2.9Compare Source
@schematics/angular
@angular/build
v18.2.8Compare Source
@schematics/angular
index.csr.htmlin resources asset group@angular/build
Ctrl + Cnot terminating dev-server with SSRv18.2.7Compare Source
@schematics/angular
@angular/build
animateto valid self-closing elementsv18.2.6Compare Source
@angular/build
v18.2.5Compare Source
@angular/build
5.4.6v18.2.4Compare Source
@angular/build
v18.2.3Compare Source
@angular-devkit/build-angular
webpack-dev-middlewareto7.4.2v18.2.2Compare Source
Breaking Changes
@angular/ssr
The server-side bootstrapping process has been changed to eliminate the reliance on a global platform injector.
Before:
After:
@angular-devkit/build-angular
@angular/build
@angular/ssr
v18.2.1Compare Source
@angular-devkit/build-angular
v18.2.0Compare Source
@schematics/angular
@angular/build
v18.1.4Compare Source
@angular/build
v18.1.3Compare Source
@angular/build
nonceattribute to script tags when inline critical CSS is disabledextract-i18nbuilder for librariesv18.1.2Compare Source
@angular/build
v18.1.1Compare Source
@angular-devkit/build-angular
@angular/build
v18.1.0Compare Source
@angular/cli
@schematics/angular
@angular/build
--inspectoption to the dev-serverv18.0.7Compare Source
@angular/cli
ng updateto keep newline at the end of package.json@angular-devkit/build-angular
5.29.2@angular/build
v18.0.6Compare Source
@angular/build
v18.0.5Compare Source
@schematics/angular
@angular-devkit/build-angular
@angular/build
.mjsfiles when using Vitev18.0.4Compare Source
@angular/build
@angular/localize/initv18.0.3Compare Source
@angular/cli
schema.jsonoptions to parsed command, also when a version is passed tong add <package>@​<version>@angular/build
v18.0.2Compare Source
@schematics/angular
assetsoption correctly for new applications@angular/build
@warnlocation@angular/pwa
iconslocation to matchassetsbuilder optionv18.0.1Compare Source
@schematics/angular
@angular/build
polyfillsoption asstringduringng servev18.0.0Compare Source
Breaking Changes
@angular/cli
ng doccommand has been removed without a replacement. To perform searches, please visit www.angular.dev@angular-devkit/build-angular
By default, the index.html file is no longer emitted in the browser directory when using the application builder with SSR. Instead, an index.csr.html file is emitted. This change is implemented because in many cases server and cloud providers incorrectly treat the index.html file as a statically generated page. If you still require the old behavior, you can use the
indexoption to specify theoutputfile name.The support for the legacy Sass build pipeline, previously accessible via
NG_BUILD_LEGACY_SASSwhen utilizing webpack-based builders, hasConfiguration
📅 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 is behind base branch, 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.