Use of Cache Containing Sensitive Information Affecting @angular/common package, versions <20.3.28>=21.0.0 <21.2.20>=22.0.0 <22.1.1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-ANGULARCOMMON-19778383
- published14 Sept 2026
- disclosed10 Sept 2026
- creditUnknown
Introduced: 10 Sep 2026
NewCVE-2026-88059 (opens in a new tab)How to fix?
Upgrade @angular/common to version 20.3.28, 21.2.20, 22.1.1 or higher.
Overview
Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information via the HttpTransferCache process. An attacker can access sensitive user-specific information by exploiting a scenario where a child HttpClient delegates requests to a parent client that injects authentication credentials, resulting in authenticated responses being cached and served to unauthorized users. This is only exploitable if all of the following conditions are met: Server-Side Rendering (SSR) with hydration is enabled, a hierarchical HttpClient configuration with withRequestsMadeViaParent() is used, authentication credentials are injected by a parent interceptor, and SSR HTML responses are cached by a shared caching layer (such as a CDN or reverse proxy).
Workaround
This vulnerability can be mitigated by attaching authentication credentials directly within the child client, applying explicit cache filters on the child client to exclude sensitive endpoints, or disabling HTTP transfer cache for routes handling user-authenticated data and ensuring SSR responses set appropriate cache-control headers.