Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By GitHub_M

  2. · 2 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-59052, by who scored it
Scored byCVSSScoreVector
GitHub_MCNA (assigner)4.0High7.1CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
NVDNVD · Deferred4.0High7.1CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS (exploitation in 30 days)
0.37% · top 69% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • angular · angular

    • affected @angular/platform-server >= 16.0.0-next.0, < 18.2.14
    • affected @angular/platform-server >= 20.0.0-next.0, < 20.3.0
    • affected @angular/platform-server >= 19.0.0-next.0, < 19.2.15
    • affected @angular/platform-server >= 21.0.0-next.0, < 21.0.0-next.3
    • affected @angular/ssr >= 17.0.0-next.0, < 18.2.21
    • affected @angular/ssr >= 19.0.0-next.0, < 19.2.16
    • affected @angular/ssr >= 20.0.0-next.0, < 20.3.0
    • affected @angular/ssr >= 21.0.0-next.0, < 21.0.0-next.3
    • affected @nguniversal/common >= 16.0.0-next.0, <= 16.2.0

Affected packages

From reviewed advisories of the GitHub Advisory Database.

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-59052 badge
[![CVE-2025-59052](https://cveledger.app/badge/CVE-2025-59052.svg)](https://cveledger.app/cve/CVE-2025-59052)

Record last updated .