CVE-2025-59052 Details
Description
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. 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 APIs `bootstrapApplication`, `getPlatform`, and `destroyPlatform` were vulnerable and required SSR-only breaking changes. The issue has been patched in all active release lines as well as in the v21 prerelease. Patched packages include `@angular/platform-server` 21.0.0-next.3, 20.3.0, 19.2.15, and 18.2.14 and `@angular/ssr` 21.0.0-next.3, 20.3.0, 19.2.16, and 18.2.21. Several workarounds are available. Disable SSR via Server Routes or builder options, remove any asynchronous behavior from custom `bootstrap` functions, remove uses of `getPlatform()` in application code, and/or ensure that the server build defines `ngJitMode` as false.
A race condition vulnerability has been identified in Angular's server-side rendering (SSR) process, specifically within the platform injector that manages request-specific state. This vulnerability, present in versions 16.0.0-next.0 prior to 18.2.14, 20.0.0-next.0 prior to 20.3.0, 19.0.0-next.0 prior to 19.2.15, and 21.0.0-next.0 prior to 21.0.0-next.3, can lead to cross-request data leakage. When multiple requests are handled simultaneously, they may unintentionally share or overwrite the global injector state, causing one request to receive data intended for another. This could result in the unintentional disclosure of data or tokens included in the rendered page or response headers. An attacker with network access could exploit this by sending numerous requests and analyzing the responses for leaked information.
The vulnerability has been patched in all active release lines, including version 21.0.0-next.3. Instructions for updating to the patched versions are available in the Angular documentation.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Sep 10, 2025CISA-ADP
Assessed Sep 10, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/angular/angular-cli/pull/31108 | [email protected] | Issue TrackingVendor |
| https://github.com/angular/angular/pull/63562 | [email protected] | Issue TrackingVendor |
| https://github.com/angular/angular/security/advisories/GHSA-68x2-mx4q-78m7 | [email protected] | AdvisoryRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| @angular/platform-server | All versions |
CPE
Remediation
| |
| @angular/ssr | >= 16.0.0-next.0, < 18.2.14 (semver) >= 20.0.0-next.0, < 20.3.0 (semver) >= 19.0.0-next.0, < 19.2.15 (semver) >= 21.0.0-next.0, < 21.0.0-next.3 (semver) |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Sep 10, 2025 | New CVE Received | [email protected] |
Volerion