Quick answers
- Is CVE-2026-44643 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44643 being exploited in the wild.
- How severe is CVE-2026-44643?
- Critical severity, with a CVSS score of 10, published 11 May 2026.
- Which products and versions are affected?
- angular-expressions (npm) SEMVER:introduced=0,fixed=1.5.2; Peerigon Angular-Expressions < 1.5.2, <= 1.5.1.
- Is there a fix for CVE-2026-44643?
- Yes. angular-expressions (npm): upgrade to 1.5.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44643 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44643?
- Check whether you run angular-expressions (npm) or Peerigon Angular-Expressions at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- angular-expressions (npm): upgrade to 1.5.2 or later
npm install angular-expressions@1.5.2
Technical details
A sandbox escape vulnerability exists in the angular-expressions library (an npm package) prior to version 1.5.2. The vulnerability is classified as Eval Injection (CWE-95) and occurs when the library incorrectly neutralizes code syntax within filters. An attacker can provide a malicious expression that leverages these filters to break out of the intended sandbox environment. This allows for arbitrary code execution on the host system. The issue is reachable over the network without authentication if the application evaluates user-supplied input through the library's compile function. The vulnerability is fixed in version 1.5.2.
Affected products
- peerigon angular-expressions < 1.5.2
Identifiers
- CVE-2026-44643
- GHSA-pw8r-6689-xvf4
Timeline
- 2026-05-07: advisory: GitHub Security Advisory published by maintainer
- 2026-05-11: disclosed: CVE published to NVD