es5-ext vulnerable to Regular Expression Denial of Service in `function#copy` and `function#toStringTokens`GHSA-4gmj-3p3h-gm8h
Fix: medikoo/es5-ext@3551cddGHSA-4gmj-3p3h-gm8h is a Uncontrolled Resource Consumption vulnerability in es5-ext. A fix is available for es5-ext — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-4gmj-3p3h-gm8h.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
es5-extnpmDescription
Impact
Passing functions with very long names or complex default argument names into function#copy orfunction#toStringTokens may put script to stall
Patches
Fixed with https://github.com/medikoo/es5-ext/commit/3551cdd7b2db08b1632841f819d008757d28e8e2 and https://github.com/medikoo/es5-ext/commit/a52e95736690ad1d465ebcd9791d54570e294602 Published with v0.10.63
Workarounds
No real workaround aside of refraining from using above utilities.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | es5-ext | ≥ 0.10.0&&< 0.10.63 | 0.10.63npm install es5-ext@0.10.63 |
Affected Products
es5-extmedikooDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for es5-ext, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update es5-ext to 0.10.63 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4gmj-3p3h-gm8h is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-4gmj-3p3h-gm8h in your dependencies?
Find it across npm, including transitive dependencies.