angular-common

Ecosystem: npm

Downloads: 25.87 Mln

Vulnerabilities from the last (months)
  • 0CriticalAffects 0 versions
  • 6HighAffects 25 versions
  • 0MediumAffects 0 versions
  • 2ModerateAffects 7 versions
  • 0LowAffects 0 versions
Severity distribution (all time)
8vulnerabilities
  • Critical0 (0.0%)
  • High6 (75.0%)
  • Medium0 (0.0%)
  • Moderate2 (25.0%)
  • Low0 (0.0%)

Monthly breakdown

  • Critical
  • High
  • Medium
  • Moderate
  • Low
  • 1 vulnerabilities
    • Critical: 0
    • High: 0
    • Medium: 0
    • Moderate: 1
    • Low: 0
  • 1 vulnerabilities
    • Critical: 0
    • High: 0
    • Medium: 0
    • Moderate: 1
    • Low: 0
  • 1 vulnerabilities
    • Critical: 0
    • High: 1
    • Medium: 0
    • Moderate: 0
    • Low: 0
  • 4 vulnerabilities
    • Critical: 0
    • High: 4
    • Medium: 0
    • Moderate: 0
    • Low: 0
  • 1 vulnerabilities
    • Critical: 0
    • High: 1
    • Medium: 0
    • Moderate: 0
    • Low: 0

Vulnerabilities (8)

Known vulnerabilities affecting angular-common, based on data from OSV.

Vulnerabilities affecting angular-common
IDSeveritySummaryAffected versionsPublishedSource
GHSA-jfgx-762w-99vrModerate@angular/common: XSRF Token Leakage via URL Parsing Discrepancy in Angular HTTP Client (Incomplete fix for CVE-2025-66035)An incomplete fix for [GHSA-58c5-g7wp-6w37](https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37) (`CVE-2025-66035`) in `@angular/common`'s HTTP Client (`HttpClient`) allows Cross-Site Request Forgery (XSRF) tokens to be leaked to attacker-controlled cross-origin domains when requests use URLs that exploit parsing discrepancies between regular expressions and the browser's WHATWG URL parser. ### Technical Description To address `CVE-2025-66035`, `xsrfInterceptorFn` introduced a regular expression (`const ABSOLUTE_URL_REGEX = /^(?:https?:)?\/\//i`) to detect and skip abs
  • >= 21.0.0, < 21.0.3
  • >= 20.0.0, < 20.3.34
  • <= 19.2.25
GitHub (opens in a new tab)
GHSA-p297-fm68-3q8cModerateAngular: Information Leak via `HttpTransferCache` Bypass When Using `withRequestsMadeViaParent`A security bypass vulnerability was discovered in `@angular/common` when Server-Side Rendering (SSR) and hydration are enabled in applications using a hierarchical `HttpClient` configuration with `withRequestsMadeViaParent()`. The `HttpTransferCache` utility optimizes hydration by caching outgoing HTTP requests performed during SSR and transferring the cached state to the client-side application via `TransferState` (serialized as JSON in `<script id="ng-state">`). Following the remediation of [CVE-2026-50170](https://github.com/angular/angular/security/advisories/GHSA-q6f4-qqrg-jv6x), `HttpTr
  • >= 22.0.0, < 22.1.1
  • >= 21.0.0, < 21.2.20
  • >= 20.0.0, < 20.3.28
  • <= 19.2.25
GitHub (opens in a new tab)
GHSA-jhpw-976m-542jHighAngular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State PoisoningAngular's `HttpTransferCache` caches HTTP requests made during Server-Side Rendering (SSR) so that they can be reused during client-side hydration. During SSR, `HttpTransferCache` previously generated identical key material for distinct request parameters when repeated values were present because repeated values were joined with commas: ```ts new HttpParams().set('role', 'user,admin') new HttpParams().append('role', 'user').append('role', 'admin') ``` Both requests previously serialized as `role=user,admin`, allowing distinct `HttpClient` requests to produce the same transfer-cache key mate
  • >= 22.0.0-next.0, < 22.0.2
  • >= 21.0.0-next.0, < 21.2.19
  • >= 20.0.0-next.0, < 20.3.27
  • <= 19.2.25
GitHub (opens in a new tab)
GHSA-39pv-4j6c-2g6vHigh@angular/common: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State PoisoningAngular's `HttpTransferCache` caches HTTP requests made during Server-Side Rendering (SSR) so that they can be reused during client-side hydration. This avoids repeating the same HTTP requests on the client. The cached responses are stored in `TransferState` using a cache key generated by hashing request properties (method, response type, mapped URL, serialized body, and sorted query parameters). The cache keys are generated using a weak 32-bit DJB2-like polynomial rolling hash. The 32-bit hash space is extremely small, allowing attackers to find hash collisions. An attacker can easily find
  • >= 22.0.0-next.0, < 22.0.1
  • >= 21.0.0-next.0, < 21.2.17
  • >= 20.0.0-next.0, < 20.3.25
  • <= 19.2.25
GitHub (opens in a new tab)
GHSA-48r7-hpm6-gfxmHigh@angular/common: Denial of Service (DoS) via OOM in Date Formatting (formatDate)A Denial of Service (DoS) vulnerability exists in the `@angular/common` package of the Angular framework. The `formatDate` function, which is also utilized by the standard Angular `DatePipe`, does not properly limit or validate the length of the `format` parameter. When parsing a maliciously crafted, excessively long date format string (e.g., a repeating pattern or very large string), the internal parser splits the string iteratively using a regular expression loop. This results in uncontrolled resource consumption (high CPU utilization and excessive memory allocations), leading to a Denial
  • >= 22.0.0-next.0, < 22.0.1
  • >= 21.0.0-next.0, < 21.2.17
  • >= 20.0.0-next.0, < 20.3.25
  • <= 19.2.25
GitHub (opens in a new tab)
GHSA-p3vc-36g9-x9grHigh@angular/common: Denial of Service (DoS) via OOM in Number Formatting (digitsInfo)A Denial of Service (DoS) vulnerability exists in the `@angular/common` package of Angular. The `formatNumber` function, which is also utilized by `DecimalPipe`, `PercentPipe`, and `CurrencyPipe`, does not properly validate the upper bounds of the `digitsInfo` parameter. Specifically, the minimum and maximum fraction digits parsed from the `digitsInfo` string (e.g., `1.2-4`) are converted to integers and used without limits. When parsing a maliciously crafted `digitsInfo` string with excessively large fraction digit values (e.g., `1.200000000-200000000`), the internal `roundNumber` function a
  • >= 22.0.0-next.0, < 22.0.0-rc.2
  • >= 20.0.0-next.0, < 20.3.22
  • >= 19.0.0-next.0, < 19.2.23
  • <= 18.2.14
  • >= 21.0.0-next.0, < 21.2.15
GitHub (opens in a new tab)
GHSA-q6f4-qqrg-jv6xHigh@angular/common: Information Leak via Default Caching of Credentialed Requests in HttpTransferCacheA vulnerability was discovered in `@angular/common` when Server-Side Rendering (SSR) and hydration are enabled. The `HttpTransferCache` utility optimizes hydration by caching outgoing HTTP requests performed during SSR and transferring the cached state to the client-side application via `TransferState`. However, the caching mechanism fails to inspect the `withCredentials` flag or the `Cookie` header of outgoing requests. As a result, credentialed, user-specific responses may be cached by default in the shared `TransferState` payload. When these responses are serialized into the HTML, any cach
  • >= 22.0.0-next.0, < 22.0.0-rc.2
  • >= 20.0.0-next.0, < 20.3.22
  • >= 19.0.0-next.0, < 19.2.23
  • <= 18.2.14
  • >= 21.0.0-next.0, < 21.2.15
GitHub (opens in a new tab)
GHSA-58c5-g7wp-6w37HighAngular is Vulnerable to XSRF Token Leakage via Protocol-Relative URLs in Angular HTTP ClientThe vulnerability is a **Credential Leak by App Logic** that leads to the **unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token** to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (`http://` or `https://`) to determine if it is cross-origin. If the URL starts with protocol-relative URL (`//`), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the `X-XSRF-TOKEN` header. ### Impact The token leakage completely bypasses An
  • >= 21.0.0-next.0, < 21.0.1
  • >= 20.0.0-next.0, < 20.3.14
  • < 19.2.16
GitHub (opens in a new tab)
  • GHSA-jfgx-762w-99vrModerate
    @angular/common: XSRF Token Leakage via URL Parsing Discrepancy in Angular HTTP Client (Incomplete fix for CVE-2025-66035)
    • >= 21.0.0, < 21.0.3
    • >= 20.0.0, < 20.3.34
    • +1 more
    Affected versions:
    • >= 21.0.0, < 21.0.3
    • >= 20.0.0, < 20.3.34
    • <= 19.2.25

    An incomplete fix for [GHSA-58c5-g7wp-6w37](https://github.com/angular/angular/security/advisories/GHSA-58c5-g7wp-6w37) (`CVE-2025-66035`) in `@angular/common`'s HTTP Client (`HttpClient`) allows Cross-Site Request Forgery (XSRF) tokens to be leaked to attacker-controlled cross-origin domains when requests use URLs that exploit parsing discrepancies between regular expressions and the browser's WHATWG URL parser. ### Technical Description To address `CVE-2025-66035`, `xsrfInterceptorFn` introduced a regular expression (`const ABSOLUTE_URL_REGEX = /^(?:https?:)?\/\//i`) to detect and skip abs

    CVE: CVE-2026-111753

  • GHSA-p297-fm68-3q8cModerate
    Angular: Information Leak via `HttpTransferCache` Bypass When Using `withRequestsMadeViaParent`
    • >= 22.0.0, < 22.1.1
    • >= 21.0.0, < 21.2.20
    • +2 more
    Affected versions:
    • >= 22.0.0, < 22.1.1
    • >= 21.0.0, < 21.2.20
    • >= 20.0.0, < 20.3.28
    • <= 19.2.25

    A security bypass vulnerability was discovered in `@angular/common` when Server-Side Rendering (SSR) and hydration are enabled in applications using a hierarchical `HttpClient` configuration with `withRequestsMadeViaParent()`. The `HttpTransferCache` utility optimizes hydration by caching outgoing HTTP requests performed during SSR and transferring the cached state to the client-side application via `TransferState` (serialized as JSON in `<script id="ng-state">`). Following the remediation of [CVE-2026-50170](https://github.com/angular/angular/security/advisories/GHSA-q6f4-qqrg-jv6x), `HttpTr

    CVE: CVE-2026-88059

  • GHSA-jhpw-976m-542jHigh
    Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning
    • >= 22.0.0-next.0, < 22.0.2
    • >= 21.0.0-next.0, < 21.2.19
    • +2 more
    Affected versions:
    • >= 22.0.0-next.0, < 22.0.2
    • >= 21.0.0-next.0, < 21.2.19
    • >= 20.0.0-next.0, < 20.3.27
    • <= 19.2.25

    Angular's `HttpTransferCache` caches HTTP requests made during Server-Side Rendering (SSR) so that they can be reused during client-side hydration. During SSR, `HttpTransferCache` previously generated identical key material for distinct request parameters when repeated values were present because repeated values were joined with commas: ```ts new HttpParams().set('role', 'user,admin') new HttpParams().append('role', 'user').append('role', 'admin') ``` Both requests previously serialized as `role=user,admin`, allowing distinct `HttpClient` requests to produce the same transfer-cache key mate

    CVE: CVE-2026-68945

  • GHSA-39pv-4j6c-2g6vHigh
    @angular/common: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning
    • >= 22.0.0-next.0, < 22.0.1
    • >= 21.0.0-next.0, < 21.2.17
    • +2 more
    Affected versions:
    • >= 22.0.0-next.0, < 22.0.1
    • >= 21.0.0-next.0, < 21.2.17
    • >= 20.0.0-next.0, < 20.3.25
    • <= 19.2.25

    Angular's `HttpTransferCache` caches HTTP requests made during Server-Side Rendering (SSR) so that they can be reused during client-side hydration. This avoids repeating the same HTTP requests on the client. The cached responses are stored in `TransferState` using a cache key generated by hashing request properties (method, response type, mapped URL, serialized body, and sorted query parameters). The cache keys are generated using a weak 32-bit DJB2-like polynomial rolling hash. The 32-bit hash space is extremely small, allowing attackers to find hash collisions. An attacker can easily find

    CVE: CVE-2026-54266

  • GHSA-48r7-hpm6-gfxmHigh
    @angular/common: Denial of Service (DoS) via OOM in Date Formatting (formatDate)
    • >= 22.0.0-next.0, < 22.0.1
    • >= 21.0.0-next.0, < 21.2.17
    • +2 more
    Affected versions:
    • >= 22.0.0-next.0, < 22.0.1
    • >= 21.0.0-next.0, < 21.2.17
    • >= 20.0.0-next.0, < 20.3.25
    • <= 19.2.25

    A Denial of Service (DoS) vulnerability exists in the `@angular/common` package of the Angular framework. The `formatDate` function, which is also utilized by the standard Angular `DatePipe`, does not properly limit or validate the length of the `format` parameter. When parsing a maliciously crafted, excessively long date format string (e.g., a repeating pattern or very large string), the internal parser splits the string iteratively using a regular expression loop. This results in uncontrolled resource consumption (high CPU utilization and excessive memory allocations), leading to a Denial

    CVE: CVE-2026-54268

  • GHSA-p3vc-36g9-x9grHigh
    @angular/common: Denial of Service (DoS) via OOM in Number Formatting (digitsInfo)
    • >= 22.0.0-next.0, < 22.0.0-rc.2
    • >= 20.0.0-next.0, < 20.3.22
    • +3 more
    Affected versions:
    • >= 22.0.0-next.0, < 22.0.0-rc.2
    • >= 20.0.0-next.0, < 20.3.22
    • >= 19.0.0-next.0, < 19.2.23
    • <= 18.2.14
    • >= 21.0.0-next.0, < 21.2.15

    A Denial of Service (DoS) vulnerability exists in the `@angular/common` package of Angular. The `formatNumber` function, which is also utilized by `DecimalPipe`, `PercentPipe`, and `CurrencyPipe`, does not properly validate the upper bounds of the `digitsInfo` parameter. Specifically, the minimum and maximum fraction digits parsed from the `digitsInfo` string (e.g., `1.2-4`) are converted to integers and used without limits. When parsing a maliciously crafted `digitsInfo` string with excessively large fraction digit values (e.g., `1.200000000-200000000`), the internal `roundNumber` function a

    CVE: CVE-2026-50171

  • GHSA-q6f4-qqrg-jv6xHigh
    @angular/common: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache
    • >= 22.0.0-next.0, < 22.0.0-rc.2
    • >= 20.0.0-next.0, < 20.3.22
    • +3 more
    Affected versions:
    • >= 22.0.0-next.0, < 22.0.0-rc.2
    • >= 20.0.0-next.0, < 20.3.22
    • >= 19.0.0-next.0, < 19.2.23
    • <= 18.2.14
    • >= 21.0.0-next.0, < 21.2.15

    A vulnerability was discovered in `@angular/common` when Server-Side Rendering (SSR) and hydration are enabled. The `HttpTransferCache` utility optimizes hydration by caching outgoing HTTP requests performed during SSR and transferring the cached state to the client-side application via `TransferState`. However, the caching mechanism fails to inspect the `withCredentials` flag or the `Cookie` header of outgoing requests. As a result, credentialed, user-specific responses may be cached by default in the shared `TransferState` payload. When these responses are serialized into the HTML, any cach

    CVE: CVE-2026-50170

  • GHSA-58c5-g7wp-6w37High
    Angular is Vulnerable to XSRF Token Leakage via Protocol-Relative URLs in Angular HTTP Client
    • >= 21.0.0-next.0, < 21.0.1
    • >= 20.0.0-next.0, < 20.3.14
    • +1 more
    Affected versions:
    • >= 21.0.0-next.0, < 21.0.1
    • >= 20.0.0-next.0, < 20.3.14
    • < 19.2.16

    The vulnerability is a **Credential Leak by App Logic** that leads to the **unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token** to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (`http://` or `https://`) to determine if it is cross-origin. If the URL starts with protocol-relative URL (`//`), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the `X-XSRF-TOKEN` header. ### Impact The token leakage completely bypasses An

    CVE: CVE-2025-66035

Showing 1-8 of 8 vulnerabilities