Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-32304: CWE-94: Improper Control of Generation of Code ('Code Injection') in locutusjs locutus

0
Critical
VulnerabilityCVE-2026-32304cvecve-2026-32304cwe-94
Published: Thu Mar 12 2026 (03/12/2026, 21:24:51 UTC)
Source: CVE Database V5
Vendor/Project: locutusjs
Product: locutus

Description

CVE-2026-32304 is a critical code injection vulnerability in locutusjs's locutus library versions prior to 3. 0. 14. The create_function(args, code) method unsafely passes arguments directly to the JavaScript Function constructor without sanitization, enabling arbitrary code execution. This flaw allows attackers to execute malicious code remotely without authentication or user interaction. The vulnerability affects educational JavaScript libraries that mimic standard libraries of other languages, potentially impacting development and testing environments. Although no known exploits are currently reported in the wild, the high CVSS score of 9. 8 reflects the severe risk. The issue is fixed in version 3. 0.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/20/2026, 02:41:16 UTC

Technical Analysis

CVE-2026-32304 is a critical vulnerability classified under CWE-94 (Improper Control of Generation of Code) affecting the locutus JavaScript library, which provides standard library functions from other programming languages for educational use. The vulnerability exists in the create_function(args, code) function prior to version 3.0.14, where both parameters are passed directly to the JavaScript Function constructor without any sanitization or validation. This unsafe practice allows an attacker to inject arbitrary JavaScript code that will be executed in the context of the application using locutus. Unlike the related CVE-2026-29091 affecting version 2.x via eval(), this issue specifically involves the new Function() constructor in version 3.x. The exploitation requires no authentication or user interaction and can be triggered remotely if untrusted input reaches create_function. The vulnerability impacts confidentiality, integrity, and availability by enabling full arbitrary code execution, potentially leading to data theft, system compromise, or denial of service. The flaw is resolved in locutus version 3.0.14 by implementing proper input sanitization or removing unsafe code generation practices. No public exploits have been reported yet, but the high CVSS score (9.8) indicates critical severity and ease of exploitation.

Potential Impact

The vulnerability allows remote attackers to execute arbitrary code within applications using vulnerable versions of locutus, potentially leading to complete system compromise. This can result in unauthorized data access, modification, or destruction, as well as the deployment of malware or ransomware. Since locutus is used primarily for educational purposes and to provide standard libraries from other languages in JavaScript, the impact is especially critical in development, testing, or educational environments where malicious code execution could propagate or be leveraged to attack other systems. The lack of authentication or user interaction requirements increases the risk of automated exploitation. Organizations relying on locutus in production or development pipelines may face significant operational disruption and security breaches if this vulnerability is exploited.

Mitigation Recommendations

1. Immediately upgrade locutus to version 3.0.14 or later, where the vulnerability is fixed. 2. Audit all codebases and dependencies to identify usage of create_function and replace or refactor any calls that pass untrusted input to the Function constructor. 3. Implement strict input validation and sanitization for any dynamic code generation or execution features. 4. Employ runtime application self-protection (RASP) or JavaScript sandboxing techniques to limit the impact of potential code injection. 5. Monitor application logs and network traffic for unusual behavior indicative of exploitation attempts, such as unexpected code execution or outbound connections. 6. Educate developers about the risks of dynamic code generation and encourage safer coding practices. 7. If upgrading is not immediately possible, consider applying temporary mitigations such as restricting access to vulnerable components or disabling features that invoke create_function with untrusted inputs.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-11T21:16:21.659Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69b333cf2f860ef943fdd74d

Added to database: 3/12/2026, 9:44:47 PM

Last enriched: 3/20/2026, 2:41:16 AM

Last updated: 4/27/2026, 1:27:18 AM

Views: 126

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses