CVE-2026-133695continuedev continue server-side request forgery
CVE-2026-133695 is a server-side request forgery in continuedev continue, rated low (2.3 on CVSS 4.0).
Why this priority: Low severity, with no exploitation signal.
Published · Updated · NVD status: Deferred
What it is
The server can be made to fetch an address of the attacker's choosing, including internal services and cloud metadata endpoints.
How it is reached
An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link. Success also depends on conditions the attacker does not fully control.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker make the server send requests into internal networks or cloud metadata.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- No fixed version is listed yet. Find every place continuedev continue runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- While there is no fix, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
- Warn the people who use it, and filter files and links on the way in.
Description from NVD
A vulnerability was detected in continuedev continue 2.0.0/2.1.0. Affected by this issue is the function DocsCrawler of the file core/indexing/docs/crawlers/DocsCrawler.ts of the component Docs Crawler. The manipulation of the argument startUrl/useLocalCrawling results in server-side request forgery. It is possible to launch the attack remotely. The attack requires a high level of complexity. The exploitation is known to be difficult. The vendor was contacted early about this disclosure but did not respond in any way.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Services that fetch URLs or call other hosts for a caller. The flaw sits between the application and the internal network behind it.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- People who open files and links. Mail, chat and browsers are the delivery path.
- Between the application and the internal network behind it. An attacker who crosses it can make the server send requests into internal networks or cloud metadata.
Questions to answer about your own systems
- Where does continuedev continue run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
14-day free trial
Understand how your systems connect.
See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.