← Back
CVE-2026-44643
critical
CVSS 10.0
Vulnerability in angular-expressions (CVE-2026-44643)
Summary
vulnerability in angular-expressions (CVE-2026-44643). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `1.5.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44643** has been found in angular-expressions.
Successful exploitation can lead to full system takeover. CVSS score: 10.0/10.
What to do: upgrade angular-expressions to **1.5.2** or later.
If unsure, ask your IT team or search "angular-expressions CVE-2026-44643" on the vendor's site.
CVE-2026-44643 (angular-expressions) — CWE-95 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `1.5.2` — apply immediately
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
**A vulnerability** (CWE-95) exists in angular-expressions.
📍 Affected scope
angular-expressions — .
🔥 Severity
Severity: Critical (CVSS 10.0/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **1.5.2**.
🛡️ 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-expressions' .` 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-expressions' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `angular-expressions` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade angular-expressions to 1.5.2ステージング環境で 1.5.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
angular-expressions
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.5.2"}]}]