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.
Original description
The description as published by the source.
Angular Expressions provides expressions for the Angular.JS web framework as a standalone module. Prior to 1.5.2, an attacker can write a malicious expression using filters that escapes the sandbox to execute arbitrary code on the system. This vulnerability is fixed in 1.5.2.
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-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.
A vulnerability (CWE-95) exists in angular-expressions.
Check the vendor advisory for the affected versions of angular-expressions.
Severity: Critical (CVSS 10.0/10). Successful exploitation can lead to full system takeover.
Update to 1.5.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade angular-expressions to 1.5.2ステージング環境で 1.5.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com