GHSA-4gmj-3p3h-gm8h — es5-ext
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.
es5-ext vulnerable to Regular Expression Denial of Service in `function#copy` and `function#toStringTokens`
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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
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 |
Detection & 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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4gmj-3p3h-gm8h can be triaged on real exposure rather than presence alone.
Tailored to GHSA-4gmj-3p3h-gm8h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4gmj-3p3h-gm8h in your dependencies?
O3 Security finds GHSA-4gmj-3p3h-gm8h across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.