Skip to main content
Menu
CVEs

continue path traversal in the edit tool's file path validation

CVE-2026-133693Published , updated

4.8MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

A path traversal weakness in the Edit Tool of continuedev continue lets an attacker manipulate file paths to reach locations outside the intended directory. The attack requires local access and low-privilege login, and no user interaction.

Written by a model

Original description

A weakness has been identified in continuedev continue 2.0.0/2.1.0. Affected is the function validateSearchAndReplaceFilepath of the file gui/src/util/clientTools/editImpl.ts of the component Edit Tool. Executing a manipulation can lead to path traversal. The attack requires local access. The vendor was contacted early about this disclosure but did not respond in any way.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133693 (continuedev continue Edit Tool editImpl.ts validateSearchAndReplaceFilepath path traversal), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133693 (entry last updated 2026-11-20):
Affected:
- continuedev continue: versions 2.0.0, 2.1.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133693 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133693 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vuldb.com/vuln/441419
- https://vuldb.com/vuln/441419/cti
- https://vuldb.com/cve/CVE-2026-133693
- https://vuldb.com/submit/1051554
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133693
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133693"}.

Affected versions

cve.now Index

10Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity4.8/10CVSS 4.8
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 6

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133693
RecordNVD · CVE-2026-133693
Other links 4
AdvisoryVulDB · Advisory #441419
AdvisoryVulDB · Threat intelligence #441419
AdvisoryVulDB · CVE-2026-133693 record
AdvisoryVulDB · Submission #1051554

Questions about CVE-2026-133693

Is CVE-2026-133693 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133693?

continue: versions 2.0.0, 2.1.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.