CVE-2026-5597
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA flaw has been found in griptape-ai griptape 0.19.4. This affects an unknown part of the file griptape\tools\computer\tool.py of the component ComputerTool. Executing a manipulation of the argument filename can lead to path traversal. It is possible to launch the attack remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePath traversal vulnerability in griptape-ai ComputerTool (griptape/tools/computer/tool.py) allows remote attackers to manipulate the filename argument with path traversal sequences (e.g., ../../) to access files outside the intended directory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed griptape versionRun: pip show griptape | grep Version OR python -c 'import griptape; print(griptape.__version__)'Affected if version equals 0.19.4 exactly, or falls within a range starting at 0.19.4 and below any patched version (verify against vendor advisories)
-
Locate the ComputerTool moduleSearch for the file griptape/tools/computer/tool.py in your environment: find . -path '*/griptape/tools/computer/tool.py' 2>/dev/null OR python -c 'import griptape.tools.computer.tool as t; print(t.__file__)'Affected if the file exists at the vulnerable path griptape\tools\computer\tool.py (Windows) or griptape/tools/computer/tool.py (Unix-like)
-
Verify ComputerTool is in useSearch your codebase for imports: grep -r 'from griptape.tools import ComputerTool' . OR grep -r 'ComputerTool' . --include='*.py'Affected if ComputerTool is imported and instantiated in your application code
-
Check how filename parameter is handledInspect the ComputerTool source code around file read/write operations, look for os.path.join or file open calls using the filename argument without validationAffected if the filename argument is passed directly to file operations without path traversal checks (e.g., no os.path.realpath or whitelist validation)
-
Review file access patterns in your deploymentAnalyze logs or traces where ComputerTool interacts with user-supplied filenames, check for patterns containing '../' sequencesAffected if your application passes unsanitized user input to the filename parameter of ComputerTool methods
You are affected if griptape version 0.19.4 is installed AND ComputerTool is used with user-controlled filename input that lacks path traversal validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation on the filename parameter to reject path traversal sequences; validate that the resolved path stays within the allowed directory. Upgrade to a patched version once available.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5597 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5597 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data