Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.0amended

Angular: Information Leak via HttpTransferCache Bypass When Using withRequestsMadeViaParent

CVE-2026-88059GHSA-p297-fm68-3q8c

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @angular/common

    Affected
    >= 22.0.0, < 22.1.1>= 21.0.0, < 21.2.20>= 20.0.0, < 20.3.28<= 19.2.25
    Fixed in
    22.1.1, 20.3.28, 21.2.20

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.0 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N
EPSS
  • CVE-2026-88059: 0.34% estimated exploitation activity in the next 30 days; percentile 27.39 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

A security bypass vulnerability was discovered in @angular/common when Server-Side Rendering (SSR) and hydration are enabled in applications using a hierarchical HttpClient configuration with withRequestsMadeViaParent(). The HttpTransferCache utility optimizes hydration by caching outgoing HTTP requests performed during SSR and transferring the cached state to the client-side application via TransferState (serialized as JSON in <script id="ng-state"). Following the remediation of CVE-2026-50170, HttpTransferCache automatically skips caching requests that contain authentication headers or credentials (Authorization, Cookie, withCredentials, etc.). However, when a child HttpClient delegates to a parent client via withRequestsMadeViaParent(), the child's TransferCache interceptor evaluates whether the request is eligible for caching before delegating to the parent client's interceptor chain. If an outgoing request originates as anonymous from the child client, the child TransferCache…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-p297-fm68-3q8c

  2. Revision 2 · amended ·

    Amended from osv record GHSA-p297-fm68-3q8c

  3. Revision 1 · created ·

    Published from ghsa record GHSA-p297-fm68-3q8c

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-88059

Advisory: Angular: Information Leak via `HttpTransferCache` Bypass When Using `withRequestsMadeViaParent`
IDs: CVE-2026-88059, GHSA-p297-fm68-3q8c
Record: https://patchnext.com/advisories/cve-2026-88059 (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: @angular/common 22.1.1, 21.2.20, 20.3.28. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @angular/common: affected >= 22.0.0, < 22.1.1; >= 21.0.0, < 21.2.20; >= 20.0.0, < 20.3.28; <= 19.2.25; fixed in 22.1.1, 20.3.28, 21.2.20

## Suggested inspection (read-only)
- `npm ls @angular/common --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @angular/common.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p297-fm68-3q8c (GitHub-reviewed advisory GHSA-p297-fm68-3q8c lists affected ranges: npm @angular/common >=22.0.0 =21.0.0 =20.0.0 =0 <=19.2.25)
- Verified: https://osv.dev/vulnerability/GHSA-p297-fm68-3q8c (OSV record GHSA-p297-fm68-3q8c lists affected ranges: npm @angular/common >=22.0.0 =21.0.0 =20.0.0 =0 <=19.2.25)

Commands are suggestions: review each one before running it.

Loading voting…