GHSA-w7h5-55jg-cq2f — @tygo-van-den-hurk/slyde
Fix: Tygo-van-den-Hurk/Slyde@e4c215bGHSA-w7h5-55jg-cq2f is a CWE-829 vulnerability in @tygo-van-den-hurk/slyde. A fix is available for @tygo-van-den-hurk/slyde — see the affected versions and patch details below.
Improper Control of Generation of Code ('Code Injection') in @tygo-van-den-hurk/slyde
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-w7h5-55jg-cq2f.
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.
@tygo-van-den-hurk/slydenpmDescription
Impact
This is a remote code execution (RCE) vulnerability. Node.js automatically imports **/*.plugin.{js,mjs} files including those from node_modules, so any malicious package with a .plugin.js file could execute arbitrary code when installed or required. All projects using this loading behavior are affected, especially those installing untrusted packages.
Patches
The issue has been patched in v0.0.5. Users should upgrade to v0.0.5 or later to mitigate the vulnerability.
Workarounds
- Audit and restrict which packages are installed in
node_modules.
References
- CWE-94: Improper Control of Generation of Code
- GitHub Security Advisories documentation: https://docs.github.com/en/code-security/security-advisories
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @tygo-van-den-hurk/slyde | all versions | 0.0.5npm install @tygo-van-den-hurk/slyde@0.0.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @tygo-van-den-hurk/slyde, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @tygo-van-den-hurk/slyde to 0.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w7h5-55jg-cq2f 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-w7h5-55jg-cq2f can be triaged on real exposure rather than presence alone.
Tailored to GHSA-w7h5-55jg-cq2f. 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-w7h5-55jg-cq2f in your dependencies?
O3 Security finds GHSA-w7h5-55jg-cq2f across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.