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.
angular-expressions <= 1.5.1
The problem has been patched in version 1.5.2 of angular-expressions.
Credits go to San Gil from www.securityoffice.io who has found the issue and reported it to us.
{
"github_reviewed_at": "2026-05-11T16:20:58Z",
"github_reviewed": true,
"severity": "CRITICAL",
"nvd_published_at": "2026-05-11T16:17:36Z",
"cwe_ids": [
"CWE-95"
]
}