7.1

CVE-2025-59052: angular Race Condition

CVSS: 7.1v4.0HighDeferred
AliasesGHSA-68x2-mx4q-78m7
Published 10-09-2025Last modified 10-09-2025
Open JSON

Vulnerability summary

CVE-2025-59052 is a high (CVSS 7.1) Race Condition vulnerability in angular. EPSS estimates a 0.34% chance of exploitation in the next 30 days, higher than 25.7% of scored vulnerabilities.

Overall risk
28/100
0100
Medium · default modelHow is this calculated?
CVSS score
7.1/10
010
High · v4.0 (CVE.org)
EPSS score
0.34%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Timeline

  1. 10-09-2025
    PublishedVulnerability first disclosed.
  2. 10-09-2025
    Last modifiedVulnerability information updated.

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.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.34%

Chance of exploitation in the next 30 days

Percentile

26%

Versus all other CVEs

30-day change

0.00 pp

From 0.34% on 18-09-2026

18-09-202618-10-2026
EPSS score
0.34%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

@angular2 products
  • platform-server≥ 16.0.0-next.0, < 18.2.14 | ≥ 20.0.0-next.0, < 20.3.0 | ≥ 19.0.0-next.0, < 19.2.15 | ≥ 21.0.0-next.0, < 21.0.0-next.3
  • ssr≥ 17.0.0-next.0, < 18.2.21 | ≥ 19.0.0-next.0, < 19.2.16 | ≥ 20.0.0-next.0, < 20.3.0 | ≥ 21.0.0-next.0, < 21.0.0-next.3
@nguniversal1 product
  • common≥ 16.0.0-next.0, ≤ 16.2.0
Angular1 product
  • angular@angular/platform-server >= 16.0.0-next.0, < 18.2.14 | @angular/platform-server >= 20.0.0-next.0, < 20.3.0 | @angular/platform-server >= 19.0.0-next.0, < 19.2.15 | @angular/platform-server >= 21.0.0-next.0, < 21.0.0-next.3 | @angular/ssr >= 17.0.0-next.0, < 18.2.21 | @angular/ssr >= 19.0.0-next.0, < 19.2.16 | @angular/ssr >= 20.0.0-next.0, < 20.3.0 | @angular/ssr >= 21.0.0-next.0, < 21.0.0-next.3 | @nguniversal/common >= 16.0.0-next.0, <= 16.2.0

3 vendors · 4 products

References

5 links