CVE-2025-59052

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Angular ausnutzen, um Informationen offenzulegen.

### 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 explicit `BootstrapContext` 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 returns `null` 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: ```ts // Before: const bootstrap = () => bootstrapApplication(AppComponent, config); // After: const bootstrap = (context: BootstrapContext) => bootstrapApplication(AppComponent, config, context); ``` As is usually the case for changes to Angular, an automatic schematic will take care of these code changes as part of ng update: ```sh # For apps on Angular v20: ng update @angular/cli @angular/core # For apps on Angular v19: ng update @angular/cli@19 @angular/core@19 # For apps on Angular v18: ng update @angular/cli@18 @angular/core@18 ``` The schematic can also be invoked explicitly if the version bump was pulled in independently: ```sh # For apps on Angular v20: ng update @angular/core --name add-bootstrap-context-to-server-main # For apps on Angular v19: ng update @angular/core@19 --name add-bootstrap-context-to-server-main # For apps on Angular v18: ng update @angular/core@18 --name add-bootstrap-context-to-server-main ``` For applications that still use `CommonEngine`, the `bootstrap` property in `CommonEngineOptions` also gains the same `context` 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 use `getPlatform` or custom async logic in `bootstrap`. Angular applications should never run in this mode outside of local development. ### Patches The issue has been patched in [all active release lines](https://angular.dev/reference/releases#actively-supported-versions) 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.21 ### Workarounds * Disable SSR via [Server Routes](https://angular.dev/guide/ssr#server-routing) (v19+) or builder options. * Remove any asynchronous behavior from custom `bootstrap` functions. * Remove uses of `getPlatform()` in application code. * Ensure that the server build defines `ngJitMode` as false. ### References * https://github.com/angular/angular/pull/63562 * https://github.com/angular/angular-cli/pull/31108