CVE-2017-1000228 — ejs
CRITICALCVE-2017-1000228 is a critical-severity (CVSS 9.8) Improper Input Validation vulnerability in ejs. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for ejs — see the affected versions and patch details below.
ejs is vulnerable to remote code execution due to weak input validation
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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.
ejsnpmDescription
nodejs ejs versions older than 2.5.3 is vulnerable to remote code execution due to weak input validation in ejs.renderFile() function
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | ejs | all versions | 2.5.5npm install ejs@2.5.5 |
Affected Products
ejsejsResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ejs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ejs to 2.5.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000228 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.
Frequently Asked Questions
Is CVE-2017-1000228 in your dependencies?
Find it across npm, including transitive dependencies.