dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7235

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
A security vulnerability has been detected in ErlichLiu claude-agent-sdk-master up to b185aa7ff0d864581257008077b4010fca1747bf. Affected by this vulnerability is an unknown functionality of the file app/api/agent-output/route.ts. The manipulation of the argument outputFile leads to path traversal. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The project was informed of the problem early through an issue report but has not responded yet.

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 · high confidence

Path traversal vulnerability in the API endpoint app/api/agent-output/route.ts where the outputFile parameter is not properly validated, allowing attackers to use '../' sequences to access files outside the intended directory. This is a remote attack vector affecting the file handling functionality.

MitigationImplement strict input validation on the outputFile parameter - sanitize paths by resolving and validating that the final path remains within an allowed directory, reject paths containing traversal sequences ('../'), and use path normalization before access checks.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the vulnerable API route file
    Search the codebase for the file at path app/api/agent-output/route.ts. If this file exists, the endpoint is present in the deployment.
    Affected if The file app/api/agent-output/route.ts exists in the deployed application.
  2. Inspect the outputFile parameter handling
    Open app/api/agent-output/route.ts and examine how the outputFile query or body parameter is processed. Look for any code that reads, uses, or passes this parameter to file operations.
    Affected if The outputFile parameter is used in file operations without validation.
  3. Check for path traversal sanitization
    Within the route.ts file, search for input validation logic that handles the outputFile value. Look for path normalization, sanitization functions, or checks that reject '../' sequences.
    Affected if No validation code exists that explicitly filters or blocks '../' path traversal sequences from the outputFile parameter.
  4. Verify path containment checks
    Examine whether the code resolves the final path and validates it remains within an allowed directory before performing file access operations.
    Affected if The code does not verify that the resolved file path stays within an intended directory boundary.
  5. Compare installed version to fixed release
    Check the application version by running 'npm list' or examining package.json, then compare against any published fixed version for this CVE if available from the vendor.
    Affected if The installed version matches or falls within the affected version range and the above conditions are met.

A user is affected if the app/api/agent-output/route.ts endpoint exists and processes the outputFile parameter without rejecting '../' traversal sequences or validating the final path stays within an allowed directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the outputFile parameter - sanitize paths by resolving and validating that the final path remains within an allowed directory, reject paths containing traversal sequences ('../'), and use path normalization before access checks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7235 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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