{"id":"CVE-2026-68945","aliases":["GHSA-jhpw-976m-542j"],"url":"https://o3.security/vulnerability/CVE-2026-68945","summary":"Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning","details":"Angular'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```","published":"2026-08-03T15:58:02.299Z","modified":"2026-10-28T02:31:04.120499016Z","cvss":null,"epss":{"score":0.00122,"percentile":0.02218,"asOf":"2026-09-15"},"cisaKev":null,"exploitsKnown":0,"affectedPackages":[{"ecosystem":"npm","name":"@angular/common","fixedVersion":"22.0.2"},{"ecosystem":"npm","name":"@angular/common","fixedVersion":"21.2.19"},{"ecosystem":"npm","name":"@angular/common","fixedVersion":"20.3.27"},{"ecosystem":"npm","name":"@angular/common","fixedVersion":null}],"fix":{"url":"https://github.com/angular/angular/commit/6867f77ec779a0a24f6339ad6c775f444202103c","label":"angular/angular@6867f77"},"references":[{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68945.json"},{"type":"ADVISORY","url":"https://github.com/angular/angular/security/advisories/GHSA-jhpw-976m-542j"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68945"},{"type":"FIX","url":"https://github.com/angular/angular/commit/6867f77ec779a0a24f6339ad6c775f444202103c"},{"type":"FIX","url":"https://github.com/angular/angular/commit/948a8d6831e8920b54663ec79421da95210e0e35"},{"type":"FIX","url":"https://github.com/angular/angular/commit/a64e2883e9dc4abdac70209129be303de79e5b2b"},{"type":"FIX","url":"https://github.com/angular/angular/commit/a6c7fc5c13e6e494a4c9bd8e773b8d4b2a99b20c"},{"type":"FIX","url":"https://github.com/angular/angular/pull/68571"},{"type":"PACKAGE","url":"https://github.com/angular/angular"}],"provenance":{"sources":["OSV.dev","FIRST.org (EPSS)"],"lastVerified":"2026-10-28T02:31:04.120499016Z"}}