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

GHSA-hqjg-pww4-pcgq

GHSA-hqjg-pww4-pcgq is a Path Traversal vulnerability in @google/clasp. O3 Security confirms whether GHSA-hqjg-pww4-pcgq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

@google/clasp vulnerable to unsafe path traversal cloning or pulling a malicious script

Also known asCVE-2026-4092
Published
Mar 13, 2026
Updated
Mar 16, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected

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

@google/claspnpm
145Kdownloads / week

Description

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 pull and clone commands to verify only expected project files are modified

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@google/claspall versions3.2.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @google/clasp. 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 @google/clasp to 3.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hqjg-pww4-pcgq 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-hqjg-pww4-pcgq 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-hqjg-pww4-pcgq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 `pull` and `clone` commands to verify only expected project files are modified
O3 Security · Impact-Aware SCA

Is GHSA-hqjg-pww4-pcgq in your dependencies?

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