LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32304: Locutus: RCE via unsanitized input in create_function()

Locutus brings stdlibs of other programming languages to JavaScript for educational purposes. Prior to 3.0.14, the create_function(args, code) function passes both parameters directly to the Function constructor without any sanitization, allowing arbitrary code execution. This is distinct from CVE-2026-29091 which was call_user_func_array using eval() in v2.x. This finding affects create_function using new Function() in v3.x. This vulnerability is fixed in 3.0.14.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Locutus versions before 3.0.14 can execute attacker-controlled JavaScript if an application feeds untrusted input into create_function(). For executives, this is critical because successful abuse can compromise confidentiality, integrity, and availability. Exposure depends on whether the vulnerable library and function are reachable in your application.

Executive priority

Prioritize remediation for internet-facing or multi-tenant JavaScript services using locutus. The severity is critical, but urgency should be driven by confirmed dependency presence and whether untrusted input reaches create_function().

Technical view

create_function(args, code) passed both arguments directly into JavaScript's Function constructor without sanitization. The source bundle maps this to CWE-88 and CWE-94 with CVSS 9.8. The issue is fixed in Locutus 3.0.14 and is distinct from CVE-2026-29091 affecting call_user_func_array in v2.x.

Likely exposure

Applications using locutus before 3.0.14 are potentially exposed, especially where create_function() receives user-controlled or externally supplied values. Transitive dependency use should also be checked. The bundle does not prove exposure for any specific downstream product.

Exploitation context

The CVSS vector indicates network-reachable, low-complexity exploitation requiring no privileges or user interaction. However, the bundle marks KEV false and provides no cited evidence of active exploitation. Treat exploit status as unconfirmed, not actively exploited.

Researcher notes

Focus analysis on the v3.x create_function() path using new Function(). Do not conflate this with CVE-2026-29091, which the bundle says involved call_user_func_array and eval() in v2.x. Public sources identify the fix release but not active exploitation.

Mitigation direction

  • Upgrade locutus to version 3.0.14 or later.
  • Update lockfiles and rebuild artifacts that include locutus.
  • Remove or isolate create_function() use where possible.
  • Do not pass untrusted input into dynamic code-generation APIs.
  • Check vendor advisory and Red Hat VEX guidance for environment-specific status.

Validation and detection

  • Inventory direct and transitive locutus versions in applications and SBOMs.
  • Confirm deployed artifacts use locutus 3.0.14 or later.
  • Search code for create_function() imports or calls.
  • Trace whether request, API, or stored data can reach create_function().
  • Confirm dependency scanners flag and clear CVE-2026-32304 after upgrade.
Prepared
Confidence
high
Sources
7

Public sources used

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-88: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter 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.

Open ATT&CK lookup
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.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32304 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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: yesTechnical 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9GitHub_M
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H1.65.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-32304Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPlocutusjs: Locutus: Arbitrary code execution via unsanitized parameters in create_function
other:Red Hat severity ratingcvssV3_1
  • 2026-03-12T22:01:47.245Z: Reported to Red Hat.
  • 2026-03-12T21:24:51.730Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
locutusjslocutus< 3.0.14Listed
Weakness

CWE details

CWE-88CWE-94

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.