llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · @angular/common

GHSA-39PV-4J6C-2G6V

@angular/common: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning

Parche disponible
Descargar PNG JSON
CVSS
—
high
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche3 versionesPrimer parche a -5 d de la divulgación
Exposición158 dDesde la divulgación, 15 jun 2026, 12:24 p. m.
Detección154 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Parche 20.3.25 +2
Monitoreo
Detectada
10 jun 26
15 jun 26
10 sept 26
17 nov 26
20 nov 26
10 jun 26
21 jul 26
31 ago 26
11 oct 26
20 nov 26
FechaFaseEventoDetalle
Remediación Parche 20.3.25 @angular/common · -5 d desde divulgación
Remediación Parche 21.2.17 @angular/common · -5 d desde divulgación
Remediación Parche 22.0.1 @angular/common · -5 d desde divulgación
Divulgación Publicada GHSA-39PV-4J6C-2G6V divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

Angular's `HttpTransferCache` caches HTTP requests made during Server-Side Rendering (SSR) so that they can be reused during client-side hydration. This avoids repeating the same HTTP requests on the client. The cached responses are stored in `TransferState` using a cache key generated by hashing request properties (method, response type, mapped URL, serialized body, and sorted query parameters).

The cache keys are generated using a weak 32-bit DJB2-like polynomial rolling hash. The 32-bit hash space is extremely small, allowing attackers to find hash collisions.

An attacker can easily find a query parameter string (e.g., `q=aaCAZMMM` for a search request) that produces the exact same 32-bit hash as a sensitive endpoint (e.g., `/api/user/profile`). When a victim visits a crafted link containing the colliding parameter, the SSR process executes both the search request and the profile request. Due to the hash collision, the search response overwrites the profile response in the `TransferState` cache.

Impact

When the application attempts to retrieve the cached response for the sensitive endpoint (such as the user's profile), it receives the attacker-controlled response instead. This results in:

  • State Poisoning: The application runs with attacker-forged data, which can lead to bypassing client-side security controls or DOM-based Cross-Site Scripting (XSS) if the data is rendered unsafely.
  • Information Leakage: If the sensitive response is mistakenly associated with the attacker's search results and rendered on the page, the victim's sensitive data may be disclosed to the attacker.

### Patched Versions
* 22.0.1
* 21.2.17
* 20.3.25

Framework-Level Fix

The logic has been updated to use a cryptographically secure SHA-256 hash algorithm for generating `TransferState` cache keys in `HttpTransferCache`. The cache keys are now 256-bit hexadecimal strings.

Workarounds

If you cannot upgrade immediately, configure your `HttpClient` requests to skip transfer caching for sensitive endpoints:

this.http.get('/api/user/profile', {
  transferCache: false
});

Alternatively, disable the HTTP transfer cache globally in your application bootstrap config:


import { provideClientHydration, withNoHttpTransferCache } from '@angular/platform-browser';

export const appConfig = {
  providers: [
    provideClientHydration(
      withNoHttpTransferCache()
    )
  ]
};

### Credits
This vulnerability was discovered and reported by CodeMender from Google DeepMind https://deepmind.google/blog/introducing-codemender-an-ai-agent-for-code-security/.

Versiones

Rangos afectados

Afectada Corregida Última
@angular/common≤ 19.2.25
@angular/common≥ 20.0.0-next.0 < 20.3.25
@angular/common≥ 21.0.0-next.0 < 21.2.17
@angular/common≥ 22.0.0-next.0 < 22.0.1
19.2.25
20.0.0-next.0
20.3.25
21.0.0-next.0
21.2.17
22.0.0-next.0
22.0.1
22.2.6
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npm@angular/common
Corregida 20.3.25, 21.2.17, 22.0.1 -5 d · -5 d · -5 d 22.2.6 no afectada
Versiones corregidas20.3.2521.2.1722.0.1
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-54266
Otrahttps://github.com/angular/angular/security/advisories/GHSA-39pv-4j6c-2g6v
Otrahttps://github.com/angular/angular/pull/69153
Otrahttps://github.com/angular/angular/commit/5f36274da3f961430ae72865159afa02a1dd9133
Otrahttps://github.com/angular/angular

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.