Vulnerable Library - common-15.2.2.tgz
Angular - commonly needed directives and services
Library home page: https://registry.npmjs.org/@angular/common/-/common-15.2.2.tgz
Path to dependency file: /MangoAPI.Client/package.json
Path to vulnerable library: /MangoAPI.Client/node_modules/@angular/common/package.json
Found in HEAD commit: 0c9bb5bd04415d4d387e12646c7ce749fd8ffae2
Vulnerabilities
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2025-66035
Vulnerable Library - common-15.2.2.tgz
Angular - commonly needed directives and services
Library home page: https://registry.npmjs.org/@angular/common/-/common-15.2.2.tgz
Path to dependency file: /MangoAPI.Client/package.json
Path to vulnerable library: /MangoAPI.Client/node_modules/@angular/common/package.json
Dependency Hierarchy:
- ❌ common-15.2.2.tgz (Vulnerable Library)
Found in HEAD commit: 0c9bb5bd04415d4d387e12646c7ce749fd8ffae2
Found in base branch: main
Vulnerability Details
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. 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. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.
Publish Date: 2025-11-26
URL: CVE-2025-66035
CVSS 3 Score Details (8.6)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Release Date: 2025-11-26
Fix Resolution: https://github.com/angular/angular.git - 20.3.14,https://github.com/angular/angular.git - 19.2.16
Step up your Open Source Security Game with Mend here
CVE-2026-54266
Vulnerable Library - common-15.2.2.tgz
Angular - commonly needed directives and services
Library home page: https://registry.npmjs.org/@angular/common/-/common-15.2.2.tgz
Path to dependency file: /MangoAPI.Client/package.json
Path to vulnerable library: /MangoAPI.Client/node_modules/@angular/common/package.json
Dependency Hierarchy:
- ❌ common-15.2.2.tgz (Vulnerable Library)
Found in HEAD commit: 0c9bb5bd04415d4d387e12646c7ce749fd8ffae2
Found in base branch: main
Vulnerability Details
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 a query parameter string (e.g., "q=aaCAZMMM" for a search request) that produces the exact same 32-bit hash as a sensitive endpoint (e.g., "/api/user/profile"). When a victim visits a crafted link containing the colliding parameter, the SSR process executes both the search request and the profile request. Due to the hash collision, the search response overwrites the profile response in the "TransferState" cache. Impact When the application attempts to retrieve the cached response for the sensitive endpoint (such as the user's profile), it receives the attacker-controlled response instead. This results in: * State Poisoning: The application runs with attacker-forged data, which can lead to bypassing client-side security controls or DOM-based Cross-Site Scripting (XSS) if the data is rendered unsafely. * Information Leakage: If the sensitive response is mistakenly associated with the attacker's search results and rendered on the page, the victim's sensitive data may be disclosed to the attacker. Patched Versions * 22.0.1 * 21.2.17 * 20.3.25 Framework-Level Fix The logic has been updated to use a cryptographically secure SHA-256 hash algorithm for generating "TransferState" cache keys in "HttpTransferCache". The cache keys are now 256-bit hexadecimal strings. Workarounds If you cannot upgrade immediately, configure your "HttpClient" requests to skip transfer caching for sensitive endpoints: this.http.get('/api/user/profile', { transferCache: false }); Alternatively, disable the HTTP transfer cache globally in your application bootstrap config: import { provideClientHydration, withNoHttpTransferCache } from '@angular/platform-browser'; export const appConfig = { providers: [ provideClientHydration( withNoHttpTransferCache() ) ] }; Credits This vulnerability was discovered and reported by "CodeMender from Google DeepMind" (https://deepmind.google/blog/introducing-codemender-an-ai-agent-for-code-security/).
Publish Date: 2026-06-15
URL: CVE-2026-54266
CVSS 3 Score Details (8.2)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: Low
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-39pv-4j6c-2g6v
Release Date: 2026-06-15
Fix Resolution: https://github.com/angular/angular.git - v20.3.25,https://github.com/angular/angular.git - v21.2.17
Step up your Open Source Security Game with Mend here
CVE-2026-54268
Vulnerable Library - common-15.2.2.tgz
Angular - commonly needed directives and services
Library home page: https://registry.npmjs.org/@angular/common/-/common-15.2.2.tgz
Path to dependency file: /MangoAPI.Client/package.json
Path to vulnerable library: /MangoAPI.Client/node_modules/@angular/common/package.json
Dependency Hierarchy:
- ❌ common-15.2.2.tgz (Vulnerable Library)
Found in HEAD commit: 0c9bb5bd04415d4d387e12646c7ce749fd8ffae2
Found in base branch: main
Vulnerability Details
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 of Service (DoS). Impact 1. Server-Side Rendering (SSR) In Angular applications that leverage Server-Side Rendering, an attacker can supply a malicious payload with an excessively long date format string. Processing this on the server causes high CPU usage and triggers a "JavaScript heap out of memory" crash, rendering the application unavailable to all users. 2. Client-Side Rendering (CSR) In standard client-side applications, executing the vulnerable function with an excessively long format string blocks the browser's main thread, causing the browser tab to freeze and become completely unresponsive. Patched Versions * 22.0.1 * 21.2.17 * 20.3.25 Attack Preconditions For this vulnerability to be exploitable, both of the following conditions must be met: 1. Vulnerable Component Usage: The application must format dates using the "formatDate" utility or the "DatePipe". 2. Attacker-Controlled Parameter: The date format string passed to these utilities must be customizable or directly controlled by untrusted user input (e.g., parsed from query parameters, user preferences, or API responses). If the date format is hardcoded (e.g., "'mediumDate'", "'shortTime'", or static strings) or properly validated to be within a reasonable length limit, the application is not vulnerable.
Publish Date: 2026-06-15
URL: CVE-2026-54268
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-48r7-hpm6-gfxm
Release Date: 2026-06-15
Fix Resolution: @angular/common - 21.2.17,@angular/common - 20.3.25,@angular/common - 22.0.1
Step up your Open Source Security Game with Mend here
CVE-2026-50171
Vulnerable Library - common-15.2.2.tgz
Angular - commonly needed directives and services
Library home page: https://registry.npmjs.org/@angular/common/-/common-15.2.2.tgz
Path to dependency file: /MangoAPI.Client/package.json
Path to vulnerable library: /MangoAPI.Client/node_modules/@angular/common/package.json
Dependency Hierarchy:
- ❌ common-15.2.2.tgz (Vulnerable Library)
Found in HEAD commit: 0c9bb5bd04415d4d387e12646c7ce749fd8ffae2
Found in base branch: main
Vulnerability Details
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 attempts to pad the digits array to match the requested fraction size. This results in an unbounded loop that repeatedly pushes elements into an array. Impact Successful exploitation of this vulnerability allows an attacker to trigger resource exhaustion, leading to a Denial of Service (DoS): * Server-Side Rendering (SSR): In applications using SSR (e.g., "@angular/ssr"), an attacker can crash the Node.js server process due to a "JavaScript heap out of memory" error. This affects the availability of the application for all users. * Client-Side Rendering (CSR): In standard client-side applications, the unbounded loop will block the main thread, freezing the user's browser tab and making it unresponsive. Attack Preconditions For this vulnerability to be exploitable, the following conditions must be met: 1. Vulnerable Component Usage: The application must use Angular's number formatting utilities, such as the "formatNumber" function directly, or via template pipes ("DecimalPipe", "PercentPipe", "CurrencyPipe"). 2. Attacker-Controlled Parameter: The "digitsInfo" parameter passed to these utilities must be customizable or directly controlled by untrusted user input (e.g., parsed from query parameters, user preference settings, or API responses that accept user-defined formatting options). If "digitsInfo" is trusted or limited to a known, defined range for its value, the vulnerability is not exploitable by external attackers. Patches - 22.0.0-rc.2 - 21.2.15 - 20.3.22 - 19.2.23 Credits This vulnerability was discovered and reported by "CodeMender from Google DeepMind" (https://deepmind.google/blog/introducing-codemender-an-ai-agent-for-code-security/).
Publish Date: 2026-06-15
URL: CVE-2026-50171
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-p3vc-36g9-x9gr
Release Date: 2026-06-15
Fix Resolution: https://github.com/angular/angular.git - v21.2.15,https://github.com/angular/angular.git - v19.2.23,https://github.com/angular/angular.git - v20.3.22
Step up your Open Source Security Game with Mend here
CVE-2026-50170
Vulnerable Library - common-15.2.2.tgz
Angular - commonly needed directives and services
Library home page: https://registry.npmjs.org/@angular/common/-/common-15.2.2.tgz
Path to dependency file: /MangoAPI.Client/package.json
Path to vulnerable library: /MangoAPI.Client/node_modules/@angular/common/package.json
Dependency Hierarchy:
- ❌ common-15.2.2.tgz (Vulnerable Library)
Found in HEAD commit: 0c9bb5bd04415d4d387e12646c7ce749fd8ffae2
Found in base branch: main
Vulnerability Details
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 caching layer (such as a CDN, reverse proxy, or shared server cache) that caches the SSR-rendered HTML page could inadvertently cache and leak one user's private data to other users, leading to a high-severity information disclosure vulnerability. Impact Successful exploitation allows an unauthenticated attacker to obtain sensitive, user-specific information of other authenticated users. This occurs when: * The SSR-rendered HTML containing the cached private data is stored in a shared cache (e.g., CDN, reverse proxy). * Subsequent requests for the same page receive the cached HTML containing the first user's private data. Attack Preconditions * SSR and Hydration Enabled: The Angular application must be configured to use Server-Side Rendering and hydration (e.g., using "provideClientHydration()"). * Credentialed Requests during SSR: The application must perform HTTP requests that require user-specific authentication (using cookies or "withCredentials: true") during the initial server-side render. * Shared Caching: The application's HTML responses must be cached by a shared caching layer (CDN, reverse proxy, or server-side cache) without proper cache-control headers to distinguish authenticated users. Patches - 22.0.0-rc.2 - 21.2.15 - 20.3.22 - 19.2.23
Publish Date: 2026-06-15
URL: CVE-2026-50170
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Origin: GHSA-q6f4-qqrg-jv6x
Release Date: 2026-06-15
Fix Resolution: https://github.com/angular/angular.git - v21.2.15,https://github.com/angular/angular.git - v19.2.23,https://github.com/angular/angular.git - v20.3.22
Step up your Open Source Security Game with Mend here
Angular - commonly needed directives and services
Library home page: https://registry.npmjs.org/@angular/common/-/common-15.2.2.tgz
Path to dependency file: /MangoAPI.Client/package.json
Path to vulnerable library: /MangoAPI.Client/node_modules/@angular/common/package.json
Found in HEAD commit: 0c9bb5bd04415d4d387e12646c7ce749fd8ffae2
Vulnerabilities
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
Vulnerable Library - common-15.2.2.tgz
Angular - commonly needed directives and services
Library home page: https://registry.npmjs.org/@angular/common/-/common-15.2.2.tgz
Path to dependency file: /MangoAPI.Client/package.json
Path to vulnerable library: /MangoAPI.Client/node_modules/@angular/common/package.json
Dependency Hierarchy:
Found in HEAD commit: 0c9bb5bd04415d4d387e12646c7ce749fd8ffae2
Found in base branch: main
Vulnerability Details
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. 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. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.
Publish Date: 2025-11-26
URL: CVE-2025-66035
CVSS 3 Score Details (8.6)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Release Date: 2025-11-26
Fix Resolution: https://github.com/angular/angular.git - 20.3.14,https://github.com/angular/angular.git - 19.2.16
Step up your Open Source Security Game with Mend here
Vulnerable Library - common-15.2.2.tgz
Angular - commonly needed directives and services
Library home page: https://registry.npmjs.org/@angular/common/-/common-15.2.2.tgz
Path to dependency file: /MangoAPI.Client/package.json
Path to vulnerable library: /MangoAPI.Client/node_modules/@angular/common/package.json
Dependency Hierarchy:
Found in HEAD commit: 0c9bb5bd04415d4d387e12646c7ce749fd8ffae2
Found in base branch: main
Vulnerability Details
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 a query parameter string (e.g., "q=aaCAZMMM" for a search request) that produces the exact same 32-bit hash as a sensitive endpoint (e.g., "/api/user/profile"). When a victim visits a crafted link containing the colliding parameter, the SSR process executes both the search request and the profile request. Due to the hash collision, the search response overwrites the profile response in the "TransferState" cache. Impact When the application attempts to retrieve the cached response for the sensitive endpoint (such as the user's profile), it receives the attacker-controlled response instead. This results in: * State Poisoning: The application runs with attacker-forged data, which can lead to bypassing client-side security controls or DOM-based Cross-Site Scripting (XSS) if the data is rendered unsafely. * Information Leakage: If the sensitive response is mistakenly associated with the attacker's search results and rendered on the page, the victim's sensitive data may be disclosed to the attacker. Patched Versions * 22.0.1 * 21.2.17 * 20.3.25 Framework-Level Fix The logic has been updated to use a cryptographically secure SHA-256 hash algorithm for generating "TransferState" cache keys in "HttpTransferCache". The cache keys are now 256-bit hexadecimal strings. Workarounds If you cannot upgrade immediately, configure your "HttpClient" requests to skip transfer caching for sensitive endpoints: this.http.get('/api/user/profile', { transferCache: false }); Alternatively, disable the HTTP transfer cache globally in your application bootstrap config: import { provideClientHydration, withNoHttpTransferCache } from '@angular/platform-browser'; export const appConfig = { providers: [ provideClientHydration( withNoHttpTransferCache() ) ] }; Credits This vulnerability was discovered and reported by "CodeMender from Google DeepMind" (https://deepmind.google/blog/introducing-codemender-an-ai-agent-for-code-security/).
Publish Date: 2026-06-15
URL: CVE-2026-54266
CVSS 3 Score Details (8.2)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: Low
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-39pv-4j6c-2g6v
Release Date: 2026-06-15
Fix Resolution: https://github.com/angular/angular.git - v20.3.25,https://github.com/angular/angular.git - v21.2.17
Step up your Open Source Security Game with Mend here
Vulnerable Library - common-15.2.2.tgz
Angular - commonly needed directives and services
Library home page: https://registry.npmjs.org/@angular/common/-/common-15.2.2.tgz
Path to dependency file: /MangoAPI.Client/package.json
Path to vulnerable library: /MangoAPI.Client/node_modules/@angular/common/package.json
Dependency Hierarchy:
Found in HEAD commit: 0c9bb5bd04415d4d387e12646c7ce749fd8ffae2
Found in base branch: main
Vulnerability Details
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 of Service (DoS). Impact 1. Server-Side Rendering (SSR) In Angular applications that leverage Server-Side Rendering, an attacker can supply a malicious payload with an excessively long date format string. Processing this on the server causes high CPU usage and triggers a "JavaScript heap out of memory" crash, rendering the application unavailable to all users. 2. Client-Side Rendering (CSR) In standard client-side applications, executing the vulnerable function with an excessively long format string blocks the browser's main thread, causing the browser tab to freeze and become completely unresponsive. Patched Versions * 22.0.1 * 21.2.17 * 20.3.25 Attack Preconditions For this vulnerability to be exploitable, both of the following conditions must be met: 1. Vulnerable Component Usage: The application must format dates using the "formatDate" utility or the "DatePipe". 2. Attacker-Controlled Parameter: The date format string passed to these utilities must be customizable or directly controlled by untrusted user input (e.g., parsed from query parameters, user preferences, or API responses). If the date format is hardcoded (e.g., "'mediumDate'", "'shortTime'", or static strings) or properly validated to be within a reasonable length limit, the application is not vulnerable.
Publish Date: 2026-06-15
URL: CVE-2026-54268
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-48r7-hpm6-gfxm
Release Date: 2026-06-15
Fix Resolution: @angular/common - 21.2.17,@angular/common - 20.3.25,@angular/common - 22.0.1
Step up your Open Source Security Game with Mend here
Vulnerable Library - common-15.2.2.tgz
Angular - commonly needed directives and services
Library home page: https://registry.npmjs.org/@angular/common/-/common-15.2.2.tgz
Path to dependency file: /MangoAPI.Client/package.json
Path to vulnerable library: /MangoAPI.Client/node_modules/@angular/common/package.json
Dependency Hierarchy:
Found in HEAD commit: 0c9bb5bd04415d4d387e12646c7ce749fd8ffae2
Found in base branch: main
Vulnerability Details
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 attempts to pad the digits array to match the requested fraction size. This results in an unbounded loop that repeatedly pushes elements into an array. Impact Successful exploitation of this vulnerability allows an attacker to trigger resource exhaustion, leading to a Denial of Service (DoS): * Server-Side Rendering (SSR): In applications using SSR (e.g., "@angular/ssr"), an attacker can crash the Node.js server process due to a "JavaScript heap out of memory" error. This affects the availability of the application for all users. * Client-Side Rendering (CSR): In standard client-side applications, the unbounded loop will block the main thread, freezing the user's browser tab and making it unresponsive. Attack Preconditions For this vulnerability to be exploitable, the following conditions must be met: 1. Vulnerable Component Usage: The application must use Angular's number formatting utilities, such as the "formatNumber" function directly, or via template pipes ("DecimalPipe", "PercentPipe", "CurrencyPipe"). 2. Attacker-Controlled Parameter: The "digitsInfo" parameter passed to these utilities must be customizable or directly controlled by untrusted user input (e.g., parsed from query parameters, user preference settings, or API responses that accept user-defined formatting options). If "digitsInfo" is trusted or limited to a known, defined range for its value, the vulnerability is not exploitable by external attackers. Patches - 22.0.0-rc.2 - 21.2.15 - 20.3.22 - 19.2.23 Credits This vulnerability was discovered and reported by "CodeMender from Google DeepMind" (https://deepmind.google/blog/introducing-codemender-an-ai-agent-for-code-security/).
Publish Date: 2026-06-15
URL: CVE-2026-50171
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-p3vc-36g9-x9gr
Release Date: 2026-06-15
Fix Resolution: https://github.com/angular/angular.git - v21.2.15,https://github.com/angular/angular.git - v19.2.23,https://github.com/angular/angular.git - v20.3.22
Step up your Open Source Security Game with Mend here
Vulnerable Library - common-15.2.2.tgz
Angular - commonly needed directives and services
Library home page: https://registry.npmjs.org/@angular/common/-/common-15.2.2.tgz
Path to dependency file: /MangoAPI.Client/package.json
Path to vulnerable library: /MangoAPI.Client/node_modules/@angular/common/package.json
Dependency Hierarchy:
Found in HEAD commit: 0c9bb5bd04415d4d387e12646c7ce749fd8ffae2
Found in base branch: main
Vulnerability Details
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 caching layer (such as a CDN, reverse proxy, or shared server cache) that caches the SSR-rendered HTML page could inadvertently cache and leak one user's private data to other users, leading to a high-severity information disclosure vulnerability. Impact Successful exploitation allows an unauthenticated attacker to obtain sensitive, user-specific information of other authenticated users. This occurs when: * The SSR-rendered HTML containing the cached private data is stored in a shared cache (e.g., CDN, reverse proxy). * Subsequent requests for the same page receive the cached HTML containing the first user's private data. Attack Preconditions * SSR and Hydration Enabled: The Angular application must be configured to use Server-Side Rendering and hydration (e.g., using "provideClientHydration()"). * Credentialed Requests during SSR: The application must perform HTTP requests that require user-specific authentication (using cookies or "withCredentials: true") during the initial server-side render. * Shared Caching: The application's HTML responses must be cached by a shared caching layer (CDN, reverse proxy, or server-side cache) without proper cache-control headers to distinguish authenticated users. Patches - 22.0.0-rc.2 - 21.2.15 - 20.3.22 - 19.2.23
Publish Date: 2026-06-15
URL: CVE-2026-50170
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-q6f4-qqrg-jv6x
Release Date: 2026-06-15
Fix Resolution: https://github.com/angular/angular.git - v21.2.15,https://github.com/angular/angular.git - v19.2.23,https://github.com/angular/angular.git - v20.3.22
Step up your Open Source Security Game with Mend here