Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54267 medium CVSS 6.1

Cross-Site Scripting (XSS) in @angular/core (CVE-2026-54267)

Summary

Cross-site scripting in @angular/core (CVE-2026-54267). Risk of unauthorized operations or information disclosure. Exploitable via HttpClient.

Original description

The description as published by the source.

To optimize client-side bootstrap in Server-Side Rendered (SSR) environments, Angular supports Hydration via provideClientHydration(). During SSR, Angular serializes the application's runtime state (such as cached HttpClient responses) and outputs it into the HTML stream as a `` tag with a predictable identifier:


    {"some-api-url": {"body": ...}}

During client bootstrap, Angular recovers this state by looking up the element via document.getElementById('ng-state') and parsing its text content.

Because the DOM element lookup for the state container is predictable and relies solely on the ID selector (ng-state), it is susceptible to DOM Clobbering.

If the application binds untrusted user input or CMS content to element properties such as id (e.g., or) before the genuine `` tag is parsed by the browser, the attacker-controlled element takes precedence in the DOM lookup.

During hydration, when Angular calls document.getElementById('ng-state'), the browser returns the attacker's clobbered element. Angular then attempts to parse the text content or attributes of this clobbered element as JSON.

Impact

By clobbering the state element, the attacker can inject a custom JSON payload into Angular's TransferState cache. The most critical exploitation vector is poisoning the HTTP Transfer Cache.

  1. The attacker injects a clobbered ng-state element containing custom JSON.
  2. The JSON maps a key (representing a target API endp…

Source: GitHub Security Advisories (Global) 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-54267 has been found in @angular/core.
Attackers can target a specific entry point like HttpClient over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "@angular/core CVE-2026-54267" on the vendor's site.

CVE-2026-54267 (@angular/core) — CWE-79 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: HttpClient / TransferState / APP_ID
Workaround: If you cannot immediately update to a patched Angular version, apply the following workarounds:
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

Cross-site scripting (XSS) (CWE-79) exists in @angular/core. Attackers reach the vulnerable code path via HttpClient without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @angular/core. Attack surface: HttpClient / TransferState / APP_ID.

🔥 Severity

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

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Workaround: If you cannot immediately update to a patched Angular version, apply the following workarounds:

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@angular/core' . 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/core' . | grep -v node_modules

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

  2. 2
    Apply temporary workaround mitigate 
    If you cannot immediately update to a patched Angular version, apply the following workarounds:

    パッチが適用されるまでの応急処置として、If you cannot immediately update to a patched Angular version, apply the following workarounds: を実施。回避策の副作用 (機能低下) を確認した上で。

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

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

Affected packages

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

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

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