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.
CVE-2026-32304
This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(low)
- EPSS
- 43.2%
- KEV
- Not listed
Published
March 13, 2026
Last Modified
June 30, 2026
Advisory Details (5)
Auto-updated Jul 12, 20262447200 – (CVE-2026-32304) CVE-2026-32304 locutusjs: Locutus: Arbitrary code execution via unsanitized parameters in create_function
https://bugzilla.redhat.com/show_bug.cgi?id=2447200RCE via unsanitized input in create_function() (CWE-94) - distinct from CVE-2026-29091 · Advisory · locutusjs/locutus · GitHub
https://github.com/locutusjs/locutus/security/advisories/GHSA-vh9h-29pq-r5m8v3.0.14
Patch available: locutusjs/locutus v3.0.14
https://github.com/locutusjs/locutus/releases/tag/v3.0.14Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| locutus | — | 3.0.14 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 04:38 UTCEG score recompute
- 2026-06-30 04:31 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-32304?
When was CVE-2026-32304 disclosed?
Is CVE-2026-32304 actively exploited?
What is the CVSS score of CVE-2026-32304?
How do I remediate CVE-2026-32304?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32304
Is Your Infrastructure Affected by CVE-2026-32304?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.