← Back
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``.
AI summary snake-internal / snake-material-v2
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
@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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@angular/core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@angular/core` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply 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: を実施。回避策の副作用 (機能低下) を確認した上で。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@angular/core
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"19.2.25"}]}]
References
- advisory [email protected]
- package https://github.com/angular/angular
- patch [email protected]
- patch [email protected]
- web https://github.com/advisories/GHSA-rgjc-h3x7-9mwg