Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-q8j6-pwqx-pm96

HIGH

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. O3 Security confirms whether GHSA-q8j6-pwqx-pm96 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Insecure template handling in Squirrelly

Also known asCVE-2021-32819
Published
May 17, 2021
Updated
Nov 8, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
4 known

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

squirrellynpm
48Kdownloads / week

Description

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

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmsquirrellyall versions9.0.0
Exploits & PoCs
4

Research 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 dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for squirrelly. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-q8j6-pwqx-pm96 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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.

Frequently Asked Questions

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](https://securitylab.github.com/advisories/GHSL-2021-023-squirrelly/).
O3 Security · Impact-Aware SCA

Is GHSA-q8j6-pwqx-pm96 in your dependencies?

O3 detects GHSA-q8j6-pwqx-pm96 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.