CVE-2026-8770
Analyzed Analyzed - Analysis Complete
Path Traversal in ContinueDev via lsTool Component

Publication date: 2026-05-18

Last updated on: 2026-05-19

Assigner: VulDB

Description
A vulnerability was identified in continuedev continue up to 1.2.22. This affects the function lsTool of the file core/tools/implementations/lsTool.ts of the component JSON-RPC Server. Such manipulation of the argument dirPath leads to path traversal. An attack has to be approached locally. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-18
Last Modified
2026-05-19
Generated
2026-05-20
AI Q&A
2026-05-19
EPSS Evaluated
2026-05-19
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
continue continue From 1.2.0 (inc) to 1.2.22 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows local attackers to perform path traversal and read arbitrary directory contents on the host system, exposing sensitive filenames and directory structures. This exposure of sensitive system information could potentially lead to violations of data protection standards and regulations such as GDPR and HIPAA, which require safeguarding sensitive and personal data from unauthorized access.

Since the vulnerability enables bypassing access constraints and exposing sensitive information, organizations using affected versions may face compliance risks related to confidentiality and data protection mandates.


Can you explain this vulnerability to me?

CVE-2026-8770 is a Local Path Traversal and Security Policy Bypass vulnerability in the lsTool component of the Continue Core JSON-RPC server. The vulnerability occurs because the lsTool function does not enforce standard workspace boundary and security checks when handling user-provided directory paths.

This allows an attacker with local access to manipulate the dirPath argument to read arbitrary directory contents on the host system, such as sensitive directories like /etc/ or ~/.ssh/, bypassing access constraints.

The issue arises from inconsistent security enforcement: while other tools use a security check API (throwIfFileIsSecurityConcern) to validate paths, lsTool omits this check and overrides default protective blocklists, enabling unrestricted file enumeration.

An exploit can be performed by sending a malicious JSON-RPC request specifying an absolute path, which returns the full contents of that directory.


How can this vulnerability impact me? :

This vulnerability can expose sensitive system information by allowing an attacker with local access to read arbitrary directories on the host system.

  • Disclosure of sensitive filenames and directory structures, such as configuration files or SSH keys.
  • Bypassing security policies and access controls intended to protect sensitive data.
  • Potentially aiding further exploitation by revealing system details that can be used to escalate privileges or compromise the system.

How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by sending a malicious JSON-RPC request to the Continue Core server on TCP port 3000, specifying an absolute path such as /etc. If the server returns the full contents of the specified directory, it confirms the vulnerability.

An example approach is to use a Python script that crafts and sends such a JSON-RPC request targeting the lsTool component to enumerate directory contents.

Monitoring network traffic for JSON-RPC requests on TCP port 3000 that include suspicious absolute paths can also help detect exploitation attempts.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include restricting local access to the Continue Core JSON-RPC server, especially on TCP port 3000, to trusted users only.

Apply available patches or upgrade the @continuedev/core npm package to a version where this vulnerability is fixed.

Implement or enforce security checks similar to the throwIfFileIsSecurityConcern API in the lsTool component to validate and restrict directory paths.

Monitor logs and network traffic for suspicious directory enumeration attempts and block or alert on such activity.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart