Vulnerabilidades

Resumen — últimos 7 días

Vulnerabilidades nuevas2624▼ 236 respecto a la semana anterior
Críticas / altas1384▲ 151 respecto a la semana anterior
Nueva explotación activa (KEV)7▼ 3 respecto a la semana anterior
Sin puntuar (sin CVSS)56▼ 473 respecto a la semana anterior
–

5 resultados, ordenados por fecha de publicación (más recientes primero)

CVEEstadoSeveridadEPSS Explotación activaTecnologías afectadasPublicada ▼Modificada Descripción
ModificadaCrítica (10)2.1%—Safe-eval Project Safe-eval11/4/202317/6/2026
All versions of the package safe-eval are vulnerable to Sandbox Bypass due to improper input sanitization. The vulnerability is derived from prototype pollution exploitation. Exploiting this vulnerability might result in remote code execution ("RCE"). **Vulnerable functions:** __defineGetter__, stack(),…
ModificadaCrítica (10)1.1%—Safe-eval Project Safe-eval11/4/202317/6/2026
All versions of the package safe-eval are vulnerable to Prototype Pollution via the safeEval function, due to improper sanitization of its parameter content.
ModificadaCrítica (9.8)0.91%—Safe-eval Project Safe-eval20/12/202217/6/2026
All versions of package safe-eval are vulnerable to Prototype Pollution which allows an attacker to add or modify properties of the Object.prototype.Consolidate when using the function safeEval. This is because the function uses vm variable, leading an attacker to modify properties of the Object.prototype.
ModificadaCrítica (9.8)1.4%—Safe-eval Project Safe-eval21/8/202017/6/2026
This affects all versions of package safe-eval. It is possible for an attacker to run an arbitrary command on the host machine.
ModificadaCrítica (10)3.5%—Safe-eval Project Safe-eval7/6/201817/6/2026
The safe-eval module describes itself as a safer version of eval. By accessing the object constructors, un-sanitized user input can access the entire standard library and effectively break out of the sandbox.