angular-expressions
Affected
- introduced
0, fixed1.5.2(semver)
Fixed versions
1.5.2
Fix
- Fixed version
1.5.2npm install [email protected]
Advisory
Also known as: CVE-2026-44643
Angular Expressions - Remote Code Execution using filters
Impact
An attacker can write a malicious expression that escapes the sandbox to execute arbitrary code on the system.
Example of vulnerable code:
const expressions = require("angular-expressions");
const result = expressions.compile("a | __proto__")({}, {});
This should throw the error : Filter '__proto__' is not defined, however, this shows :
Uncaught SyntaxError: Unexpected identifier 'Object'
With a more complex (undisclosed) payload, one can get full access to Arbitrary code execution on the system.
Vulnerable versions :
angular-expressions <= 1.5.1
Patches
The problem has been patched in version 1.5.2 of angular-expressions.
Credits
Credits go to San Gil from www.securityoffice.io who has found the issue and reported it to us.
Critical Basis: The source's own band: CRITICAL
0, fixed 1.5.2 (semver)1.5.2
1.5.2npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0