CVE-2026-29091
Locutus remote code execution
- Published6 Mar 2026
Description
Locutus brings stdlibs of other programming languages to JavaScript for educational purposes. Prior to version 3.0.0, a remote code execution (RCE) flaw was discovered in the locutus project, specifically within the call_user_func_array function implementation. The vulnerability allows an attacker to inject arbitrary JavaScript code into the application's runtime environment. This issue stems from an insecure implementation of the call_user_func_array function (and its wrapper call_user_func), which fails to properly validate all components of a callback array before passing them to eval(). This issue has been patched in version 3.0.0.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/security/cve/CVE-2026-29091
- https://bugzilla.redhat.com/show_bug.cgi?id=2445262
- https://github.com/locutusjs/locutus/commit/977a1fb169441e35996a1d2465b512322de500ad
- https://github.com/locutusjs/locutus/security/advisories/GHSA-fp25-p6mj-qqg6
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-29091.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-29091 being actively exploited?
CVE-2026-29091 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.02%.
How severe is CVE-2026-29091?
CVE-2026-29091 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 1.02% probability of exploitation.
Which products are affected by CVE-2026-29091?
Affected products include Locutus.
How do I fix CVE-2026-29091?
Upgrade affected software to a fixed version, for example Locutus 3.0.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-29091 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.