Cyber Resilience

CVE-2026-4092

Path Traversal in Google Clasp ≤ 3.2.0

Published
13 March 2026
Modified
14 April 2026
Patch / advisory
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0046 38th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-4092 is a high-severity Path Traversal (CWE-22) vulnerability in Google Clasp. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-4092 is a path traversal vulnerability (CWE-22) in Clasp, the command-line interface tool for Google Apps Script, affecting all versions prior to 3.2.0. The flaw resides in the handling of project filenames, allowing directory traversal sequences to be processed when a specially crafted Google Apps Script project is loaded.

A remote attacker can exploit the issue by supplying a malicious project containing crafted filenames. Successful exploitation grants remote code execution on the victim's system, with the attack vector requiring user interaction such as opening or syncing the project but no authentication or special privileges.

The referenced GitHub pull request 1109 implements the fix by updating filename sanitization logic; practitioners should upgrade Clasp to version 3.2.0 or later to eliminate the traversal vectors.

EPSS for the CVE rose from a low baseline to a peak of 0.0132 on 2026-03-19 shortly after disclosure before receding to the current value of 0.0027, indicating a transient increase in exploitation interest after public release. No confirmed in-the-wild exploitation has been reported.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Path Traversal in Clasp impacting versions < 3.2.0 allows a remote attacker to perform remote code execution via a malicious Google Apps Script project containing specially crafted filenames with directory traversal sequences.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-20943Same vendor: Google
CVE-2023-21093Same vendor: Google
CVE-2025-48567Same vendor: Google
CVE-2026-3223Same vendor: Google
CVE-2025-48636Same vendor: Google
CVE-2023-30678Same vendor: Google
CVE-2025-14111Same vendor: Google
CVE-2025-1915Same vendor: Google
CVE-2025-13876Same vendor: Google
CVE-2024-49421Same vendor: Google

Affected Assets

google
clasp
≤ 3.2.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

Input validation directly neutralizes special path elements before pathname construction occurs.

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches path traversal via static/dynamic analysis.

prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

prevents

Application security requirements include rules for safe file handling and canonicalization.

prevents

Secure architecture principles require least-privilege file access and directory isolation.

prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

mitigates

Information access restriction limits which files an application may read or write.

References