Angular up to 19.2.25 /api/user/profile weak hash

Summaryinfo

A vulnerability, which was classified as critical, was found in Angular up to 19.2.25. Affected by this vulnerability is an unknown functionality of the file /api/user/profile. Executing a manipulation can lead to weak hash. The identification of this vulnerability is CVE-2026-54266. The attack may be launched remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Angular up to 19.2.25. It has been declared as critical. This vulnerability affects some unknown functionality of the file /api/user/profile. The manipulation with an unknown input leads to a weak hash vulnerability. The CWE definition for the vulnerability is CWE-328. The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack). As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability was named CVE-2026-54266 since 06/12/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1600.001.

Upgrading to version 20.0.0-next.0 20.3.25, 21.0.0-next.0 21.2.17 or 22.0.0-next.0 22.0.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-38269). Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• JavaScript Library

Name

• Angular

Version

• 19.2.0
• 19.2.1
• 19.2.2
• 19.2.3
• 19.2.4
• 19.2.5
• 19.2.6
• 19.2.7
• 19.2.8
• 19.2.9
• 19.2.10
• 19.2.11
• 19.2.12
• 19.2.13
• 19.2.14
• 19.2.15
• 19.2.16
• 19.2.17
• 19.2.18
• 19.2.19
• 19.2.20
• 19.2.21
• 19.2.22
• 19.2.23
• 19.2.24
• 19.2.25

Website

• Product: https://github.com/angular/angular/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion