Bug 2531610 (CVE-2026-88059)

Summary: CVE-2026-88059 Angular: Angular: Information Leak via HttpTransferCache Bypass
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: amctagga, ansmith, aoconnor, aruklets, aschwart, aszczucz, bniver, boliveir, doconnor, drichtar, eglynn, flucifre, gmalinko, gmeno, gotiwari, groman, janstey, jhorak, jjoyce, jpretori, jschluet, lchilton, lhh, mbenjamin, mburns, mgarciac, mhackett, mposolda, mvyas, pdelbell, pjindal, rhel-process-autobot, rmartinc, rstepani, sfeifer, sostapov, ssilvert, sthorger, vereddy, vmuzikar, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Angular. When Server-Side Rendering (SSR) and hydration are used with a hierarchical HttpClient configured with `withRequestsMadeViaParent`, the `HttpTransferCache` can improperly cache authenticated responses. This occurs because a child TransferCache stores private response data in TransferState even when a parent HttpClient chain adds credentials and skips the authenticated request. Consequently, a later unauthenticated or unauthorized visitor could receive cached HTML containing sensitive data from a previously authenticated user, leading to information disclosure.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-09-10 19:11:28 UTC 
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.