Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-88059 medium CVSS 4.0

Information Disclosure in @angular/common (CVE-2026-88059)

Summary

Vulnerability in @angular/common (CVE-2026-88059). Risk of unauthorized operations or information disclosure. Exploitable via Authorization header.

Original description

The description as published by the source.

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 ``). 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 marks the request as cacheable. When the request reaches a parent interceptor that injects sensitive authentication credentials (such as an Authorization header or API token), the parent TransferCache correctly skips caching the authenticated request. However, when the backend returns the private, authenticated response, the child TransferCache still stores the response in TransferState based on its…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-88059 has been found in @angular/common.
Attackers can target a specific entry point like Authorization header over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "@angular/common CVE-2026-88059" on the vendor's site.

CVE-2026-88059 (@angular/common) — CWE-200 / CVSS v3 4.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Authorization header / HttpClient / HttpTransferCache / TransferState
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in @angular/common. Attackers reach the vulnerable code path via Authorization header without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @angular/common. Attack surface: Authorization header / HttpClient / HttpTransferCache / TransferState.

🔥 Severity

Severity: Medium (CVSS 4.0/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@angular/common' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@angular/common' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @angular/common を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @angular/common
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details