You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.1, 21.2.17, and 20.3.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 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. This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
OR
*cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions up to (including) 18.2.14
*cpe:2.3:a:angularjs:angularjs:22.0.0:next0:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next1:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next10:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next11:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next12:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next2:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next3:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next4:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next5:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next6:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next7:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next8:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:next9:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:rc0:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:22.0.0:rc1:*:*:*:*:*:*
*cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 19.0.0 up to (excluding) 19.2.23
*cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 20.0.0 up to (excluding) 20.3.22
*cpe:2.3:a:angularjs:angularjs:*:*:*:*:*:*:*:* versions from (including) 21.0.0 up to (excluding) 21.2.15
New CVE Received from GitHub, Inc.6/22/2026 12:16:39 PM
Action
Type
Old Value
New Value
Added
Description
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.1, 21.2.17, and 20.3.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 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. This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25.