Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning

CVSS 4.0 8.8 HIGHEUVD CVSS 4.0 8.8 CVSS 4.0 · [email protected] · Secondary 8.8 HIGHCVSS 3.1 · [email protected] · Primary 6.1 MEDIUMCVSS_V4 Publisher rating HIGHFixed by @angular/common 22.0.2Fixed by @angular/common 21.2.19Fixed by @angular/common 20.3.27KEV status unknown

cve-program · CVE-2026-68945

Published

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.27, 21.2.19, and 22.0.2, HttpTransferCache comma-joins repeated request parameters, allowing semantically distinct HttpClient requests to use the same transfer-cache key and reuse a wrong backend response. This issue is fixed in versions 20.3.27, 21.2.19, and 22.0.2.

Read the publisher's advisory

euvd · EUVD-2026-52343

Published

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.27, 21.2.19, and 22.0.2, HttpTransferCache comma-joins repeated request parameters, allowing semantically distinct HttpClient requests to use the same transfer-cache key and reuse a wrong backend response. This issue is fixed in versions 20.3.27, 21.2.19, and 22.0.2.

Read the publisher's advisory

nvd · CVE-2026-68945

Published

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.27, 21.2.19, and 22.0.2, HttpTransferCache comma-joins repeated request parameters, allowing semantically distinct HttpClient requests to use the same transfer-cache key and reuse a wrong backend response. This issue is fixed in versions 20.3.27, 21.2.19, and 22.0.2.

Read the publisher's advisory

osv · GHSA-jhpw-976m-542j

Published

Angular's `HttpTransferCache` caches HTTP requests made during Server-Side Rendering (SSR) so that they can be reused during client-side hydration. During SSR, `HttpTransferCache` previously generated identical key material for distinct request parameters when repeated values were present because repeated values were joined with commas: ```ts new HttpParams().set('role', 'user,admin') new HttpParams().append('role', 'user').append('role', 'admin') ``` Both requests previously serialized as `role=user,admin`, allowing distinct `HttpClient` requests to produce the same transfer-cache key material. ### Impact In 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: - **State Poisoning**: Using incorrect or attacker-influenced cached responses for subsequent application logic. - **Cross-Request Response Reuse**: Reusing cached responses across requests with semantically different parameters. ### Patched Versions - 22.0.2 - 21.2.19 - 20.3.27 ### Workarounds If you cannot upgrade immediately, configure your `HttpClient` requests to skip transfer caching for sensitive endpoints where repeated parameter keys are used: ```ts this.http.get('/api/resource', { transferCache: false }); ``` Alternatively, disable the HTTP transfer cache globally in your application bootstrap config: ```ts import { provideClientHydration, withNoHttpTransferCache } from '@angular/platform-browser'; export const appConfig = { providers: [ provideClientHydration( withNoHttpTransferCache() ) ] }; ```

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-68945

Published

angular

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "angular",
                    "product": "angular",
                    "versions": [
                        {
                            "version": "< 20.3.27",
                            "status": "affected"
                        },
                        {
                            "version": ">= 21.0.0-next.0, < 21.2.19",
                            "status": "affected"
                        },
                        {
                            "version": ">= 22.0.0-next.0, < 22.0.2",
                            "status": "affected"
                        }
                    ]
                }

common

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "@angular",
                    "product": "common",
                    "versions": [
                        {
                            "version": "< 20.3.27",
                            "status": "affected"
                        },
                        {
                            "version": ">= 21.0.0-next.0, < 21.2.19",
                            "status": "affected"
                        },
                        {
                            "version": ">= 22.0.0-next.0, < 22.0.2",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-52343

Published

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.

Original publisher date fields

datePublished: Aug 3, 2026, 3:58:02 PM

dateUpdated: Aug 3, 2026, 4:58:26 PM

1 related source bulletins · separate from aliases

WID-SEC-W-2026-2632: Angular: Mehrere Schwachstellen

CVE-2026-68945 · CVE-2026-69149 · CVE-2026-69151

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-68945

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-345

Original publisher date fields

published: 2026-08-03T17:16:45.033

lastModified: 2026-08-11T18:13:35.950

1 source CPE criteria · context only
  • cpe:2.3:a:angular:angular:*:*:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-jhpw-976m-542j

Published

@angular/common

npm

SEMVER · introduced 22.0.0-next.0 → fixed 22.0.2

@angular/common

npm

SEMVER · introduced 21.0.0-next.0 → fixed 21.2.19

@angular/common

npm

SEMVER · introduced 20.0.0-next.0 → fixed 20.3.27

@angular/common

npm

SEMVER · introduced 0 → last_affected 19.2.25

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 08:05 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current