CVE-2024-40453: squirrelly · Code Injection
Affects squirrellySource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmsquirrellyjs/squirrellypkg:npm/squirrellyjs/squirrellyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-40453, organizations should immediately upgrade squirrellyjs to version 9.0.1 or later, where the vulnerability is fixed. Beyond patching, developers must audit all template usage to ensure that dynamic variable names or component options do not accept untrusted input without strict validation or sanitization. Implement input validation routines that whitelist acceptable variable names and reject suspicious or malformed inputs. Employ runtime application self-protection (RASP) or web application firewalls (WAFs) with custom rules to detect and block suspicious template injection patterns. Conduct thorough code reviews focusing on template rendering logic and avoid passing user-controlled data directly into template configuration options. Additionally, adopt secure coding standards that minimize dynamic code generation and leverage static analysis tools to detect potential injection flaws. Monitor application logs and network traffic for anomalous behavior indicative of exploitation attempts. Finally, maintain an up-to-date inventory of third-party libraries and dependencies to ensure timely application of security patches.
Description
squirrellyjs squirrelly v9.0.0 and fixed in v.9.0.1 was discovered to contain a code injection vulnerability via the component options.varName.