{"id":"EUVD-2026-75702","revision":"88cf5eee3f454c76b790500a9091fd68","records":[{"revision":"88cf5eee3f454c76b790500a9091fd68","observedAt":"2026-11-09T16:08:20.194+00:00","statement":{"source":"euvd","id":"EUVD-2026-75702","aliases":["CVE-2026-88059","GHSA-p297-fm68-3q8c"],"title":"Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.28, 21.2.20, and 22.1.1, Angular's @angular/common HttpTransferCache can cache an authenticate…","description":"Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.28, 21.2.20, and 22.1.1, Angular's @angular/common HttpTransferCache can cache an authenticated response when Server-Side Rendering (SSR) and hydration use a hierarchical HttpClient configured with withRequestsMadeViaParent. The child TransferCache evaluates an initially anonymous request before delegation, then a parent withInterceptors chain adds an Authorization header, cookie, or API token; although the parent cache skips the authenticated request, the child still stores the private response in TransferState serialized as JSON in the ng-state script. Exploitation requires provideClientHydration, child provideHttpClient delegation through withRequestsMadeViaParent, parent-level credential injection, and an SSR HTML response shared across users by a CDN, reverse proxy, or application cache. A later unauthenticated or unauthorized visitor can receive the cached HTML containing the earlier authenticated user's sensitive response data. Applications can mitigate by attaching credentials at the child, filtering sensitive endpoints with withHttpTransferCacheOptions, disabling transfer caching for sensitive routes, or marking personalized HTML private or no-store. This issue is fixed in versions 20.3.28, 21.2.20, and 22.1.1.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N","score":4,"severity":null}],"references":["https://github.com/angular/angular/security/advisories/GHSA-p297-fm68-3q8c","https://github.com/angular/angular/issues/69777","https://github.com/angular/angular/pull/69778","https://github.com/angular/angular/commit/c45028e44f5f3c1e0006eaccf86642deca51b2af","https://github.com/angular/angular/commit/caf616670fd20d528aa69e0131cc17d60f0cc27d","https://github.com/angular/angular/commit/e4c416c20a1cb222ce73d29c035452b257380c56","https://github.com/angular/angular/releases/tag/v20.3.28","https://github.com/angular/angular/releases/tag/v21.2.20","https://github.com/angular/angular/releases/tag/v22.1.1"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-75702","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Sep 10, 2026, 7:00:12 PM","dateUpdated":"Sep 11, 2026, 5:50:22 PM"},"relatedAdvisories":[],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2026-75702","identifiers":["EUVD-2026-75702","CVE-2026-88059","GHSA-p297-fm68-3q8c"]},"retained":false,"historicalAffected":[]}],"coverage":[]}