CVE-2026-4092 — @google/clasp
Fix: google/clasp#1109CVE-2026-4092 is a Path Traversal vulnerability in @google/clasp. A fix is available for @google/clasp — see the affected versions and patch details below.
Arbitrary File Write via Path Traversal in Google clasp leading to RCE
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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 CVE-2026-4092.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
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.
@google/claspnpmDescription
Impact
Allows an attacker to perform a "Path Traversal" attack to modify files outside the projects directory, potentially allowing for running attacker code on the developer's machine.
Patches
Fixed in version 3.2.0
Workarounds
- Only clone or pull scripts from trusted sources
- Review the output of the
pullandclonecommands to verify only expected project files are modified
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @google/clasp | all versions | 3.2.0npm install @google/clasp@3.2.0 |
Affected Products
claspgoogleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @google/clasp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @google/clasp to 3.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-4092 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2026-4092 in your dependencies?
Find it across npm, including transitive dependencies.