CVE-2026-29091: Locutus: Remote Code Execution (RCE) in locutus call_user_func_array due to Code Injection
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.
Security readout for executives and security teams
Plain-English summary
Locutus versions before 3.0.0 contain a code injection flaw that can let an attacker run arbitrary JavaScript inside an affected application. The issue is high severity because successful exploitation can compromise confidentiality, integrity, and availability. The cited sources identify version 3.0.0 as patched.
Executive priority
Prioritize remediation where locutus is used in production, especially in externally reachable services. The business risk is full application compromise after successful exploitation, but current evidence does not show known active exploitation.
Technical view
The vulnerable locutus call_user_func_array implementation, and wrapper call_user_func, did not properly validate all callback-array components before passing data to eval(). CVSS 3.1 is 8.1, with network attack vector, high complexity, no privileges, no user interaction, and high CIA impact.
Likely exposure
Exposure is most likely in JavaScript applications that depend on locutus below 3.0.0 and use call_user_func_array or call_user_func with attacker-influenced callback arrays. Indirect dependency exposure is possible but not confirmed by the bundle.
Exploitation context
The bundle does not cite active exploitation, and KEV is false. Exploitation is described as remote code execution, but CVSS marks attack complexity high. Treat internet-facing or input-driven uses of the affected functions as priority validation targets.
Researcher notes
Key research focus is reachability: vulnerable versions alone are not enough to prove exploitability. Validate whether affected functions are imported, called, and reachable with attacker-controlled callback array elements. Do not assume broader product impact beyond locutus before 3.0.0.
Mitigation direction
Upgrade locutus to version 3.0.0 or later.
Identify and remediate transitive dependencies that resolve locutus below 3.0.0.
Avoid passing attacker-controlled callback arrays into vulnerable functions before upgrade.
Check vendor advisory guidance if immediate upgrade is blocked.
Validation and detection
Inventory package manifests and lockfiles for locutus versions below 3.0.0.
Search application code for call_user_func_array and call_user_func usage.
Determine whether callback inputs can be influenced by remote users.
Confirm deployed artifacts include the patched locutus version.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.