{"id":"CVE-2026-68945","aliases":["GHSA-jhpw-976m-542j"],"title":"Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning","summary":"Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning","severity":"high","cwe":["CWE-345"],"vendor":"angular","product":"@angular/common","ecosystem":"npm","affected":["@angular/common >= 22.0.0-next.0, < 22.0.2","@angular/common >= 21.0.0-next.0, < 21.2.19","@angular/common >= 20.0.0-next.0, < 20.3.27","@angular/common <= 19.2.25"],"patched":["@angular/common 22.0.2","@angular/common 21.2.19","@angular/common 20.3.27"],"published":"2026-08-03","updated":"2026-08-03","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-jhpw-976m-542j","references":[{"url":"https://github.com/angular/angular/security/advisories/GHSA-jhpw-976m-542j"},{"url":"https://github.com/angular/angular/pull/68571"},{"url":"https://github.com/angular/angular/commit/6867f77ec779a0a24f6339ad6c775f444202103c"},{"url":"https://github.com/angular/angular/commit/948a8d6831e8920b54663ec79421da95210e0e35"},{"url":"https://github.com/angular/angular/commit/a64e2883e9dc4abdac70209129be303de79e5b2b"},{"url":"https://github.com/angular/angular/commit/a6c7fc5c13e6e494a4c9bd8e773b8d4b2a99b20c"},{"url":"https://github.com/advisories/GHSA-jhpw-976m-542j"}],"tags":["ghsa","npm"],"ingestedAt":"2026-08-03T16:26:24.202Z","epss":0.00122,"epssPercentile":0.0224,"slug":"CVE-2026-68945","body":"## Overview\n\nAngular's `HttpTransferCache` caches HTTP requests made during Server-Side Rendering (SSR) so that they can be reused during client-side hydration.\n\nDuring SSR, `HttpTransferCache` previously generated identical key material for distinct request parameters when repeated values were present because repeated values were joined with commas:\n\n```ts\nnew HttpParams().set('role', 'user,admin')\nnew HttpParams().append('role', 'user').append('role', 'admin')\n```\n\nBoth requests previously serialized as `role=user,admin`, allowing distinct `HttpClient` requests to produce the same transfer-cache key material.\n\n### Impact\n\nIn an SSR application, this cache-key ambiguity can make a later security-sensitive `HttpClient` request receive the response from an earlier semantically different request in the same render. For example, an attacker-influenced scalar-comma request can be cached and then replayed as the response for a trusted repeated-param authorization or data request to the same URL. As a result, Angular's server-rendered output can be based on the wrong backend response because the trusted request is not dispatched. This can lead to:\n\n- **State Poisoning**: Using incorrect or attacker-influenced cached responses for subsequent application logic.\n- **Cross-Request Response Reuse**: Reusing cached responses across requests with semantically different parameters.\n\n### Patched Versions\n\n- 22.0.2\n- 21.2.19\n- 20.3.27\n\n### Workarounds\n\nIf you cannot upgrade immediately, configure your `HttpClient` requests to skip transfer caching for sensitive endpoints where repeated parameter keys are used:\n\n```ts\nthis.http.get('/api/resource', {\n  transferCache: false\n});\n```\n\nAlternatively, disable the HTTP transfer cache globally in your application bootstrap config:\n\n```ts\nimport { provideClientHydration, withNoHttpTransferCache } from '@angular/platform-browser';\n\nexport const appConfig = {\n  providers: [\n    provideClientHydration(\n      withNoHttpTransferCache()\n    )\n  ]\n};\n```\n\n## Affected packages\n\n- `@angular/common >= 22.0.0-next.0, < 22.0.2`\n- `@angular/common >= 21.0.0-next.0, < 21.2.19`\n- `@angular/common >= 20.0.0-next.0, < 20.3.27`\n- `@angular/common <= 19.2.25`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `@angular/common 22.0.2`\n- `@angular/common 21.2.19`\n- `@angular/common 20.3.27`","depth":"twilight","depthScore":41,"depthScoreParts":{"impact":41.3,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}