https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T17:15:57.378477+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2024-11152 bdu:2024-11152 2026-10-06T17:15:57.381740+00:00 bdu:2024-11152 https://cve.radiocsirt.org/vuln/euvd-2026-206608 EUVD-2026-206608 2026-10-06T17:15:57.381771+00:00 EUVD-2026-206608 https://cve.radiocsirt.org/vuln/fkie_cve-2024-54152 fkie_cve-2024-54152 2026-10-06T17:15:57.381786+00:00

Angular Expressions provides expressions for the Angular.JS web framework as a standalone module. Prior to version 1.4.3, an attacker can write a malicious expression that escapes the sandbox to execute arbitrary code on the system. With a more complex (undisclosed) payload, one can get full access to Arbitrary code execution on the system. The problem has been patched in version 1.4.3 of Angular Expressions. Two possible workarounds are available. One may either disable access to `__proto__` globally or make sure that one uses the function with just one argument.

 https://cve.radiocsirt.org/vuln/ghsa-5462-4vcx-jh7j GHSA-5462-4vcx-jh7j — Angular Expressions - Remote Code Execution when using locals 2026-10-06T17:15:57.381815+00:00

Affected: npm: angular-expressions

### Impact

An attacker can write a malicious expression that escapes the sandbox to execute arbitrary code on the system.

Example of vulnerable code:

```js const expressions = require("angular-expressions"); const result = expressions.compile("__proto__.constructor")({}, {}); // result should be undefined, however for versions <=1.4.2, it returns an object. ```

With a more complex (undisclosed) payload, one can get full access to Arbitrary code execution on the system.

### Patches

The problem has been patched in version 1.4.3 of angular-expressions.

### Workarounds

There is one workaround if it not possible for you to update :

* Make sure that you use the compiled function with just one argument : ie this is not vulnerable : `const result = expressions.compile("__proto__.constructor")({});` : in this case you lose the feature of locals if you need it.

### Credits

Credits go to [JorianWoltjer](https://github.com/JorianWoltjer) who has found the issue and reported it to use. https://jorianwoltjer.com/

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-54152 Withdrawn: UBUNTU-CVE-2024-54152 2026-10-06T17:15:57.381854+00:00

Withdrawn by the publisher.

Affected: Ubuntu:16.04:LTS: angular.js, Ubuntu:18.04:LTS: angular.js, Ubuntu:20.04:LTS: angular.js, Ubuntu:22.04:LTS: angular.js, Ubuntu:24.04:LTS: angular.js, Ubuntu:25.10: angular.js, Ubuntu:25.04: angular.js

Angular Expressions provides expressions for the Angular.JS web framework as a standalone module. Prior to version 1.4.3, an attacker can write a malicious expression that escapes the sandbox to execute arbitrary code on the system. With a more complex (undisclosed) payload, one can get full access to Arbitrary code execution on the system. The problem has been patched in version 1.4.3 of Angular Expressions. Two possible workarounds are available. One may either disable access to `__proto__` globally or make sure that one uses the function with just one argument.