GHSA-q8j6-pwqx-pm96 is a high-severity (CVSS 8) Information Exposure vulnerability in squirrelly. 4 public exploit references exist, so weaponization risk is real. A fix is available for squirrelly — see the affected versions and patch details below.
Insecure template handling in Squirrelly
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.
How urgent is this, really
GHSA-q8j6-pwqx-pm96 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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.
squirrellynpmDescription
Squirrelly is a template engine implemented in JavaScript that works out of the box with ExpressJS. Squirrelly mixes pure template data with engine configuration options through the Express render API. By overwriting internal configuration options remote code execution may be triggered in downstream applications. Version 9.0.0 has a fix for this issue. For complete details refer to the referenced GHSL-2021-023.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | squirrelly | all versions | 9.0.0npm install squirrelly@9.0.0 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Squirrelly is a template engine implemented in JavaScript that works out…
Squirrelly is a template engine implemented in JavaScript that works out…
Squirrelly is a template engine implemented in JavaScript that works out…
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for squirrelly, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update squirrelly to 9.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q8j6-pwqx-pm96 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-q8j6-pwqx-pm96 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-q8j6-pwqx-pm96. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect GHSA-q8j6-pwqx-pm96
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-q8j6-pwqx-pm96 -u https://target- Template
- Nodejs Squirrelly - Remote Code Execution
- Severity
- high
- Impact
- Successful exploitation of this vulnerability could allow an attacker to execute arbitrary code on the affected system.
- Remediation
- Update to the latest version of Nodejs Squirrelly template engine to mitigate the vulnerability.
Template by ProjectDiscovery nuclei-templates (pikpikcu), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is GHSA-q8j6-pwqx-pm96 in your dependencies?
O3 Security finds GHSA-q8j6-pwqx-pm96 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.