continue information disclosure in dev data logging
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The continuedev continue software has a flaw in the DataLogger.logDevData function of its Dev Data Logging component that can lead to information disclosure. An attacker can reach it remotely, without logging in, but a user must take some action for the attack to work.
Written by a model
Original description
A flaw has been found in continuedev continue up to 2.1.0. This affects the function DataLogger.logDevData of the file core/data/log.ts of the component Dev Data Logging. This manipulation causes information disclosure. The attack can be initiated remotely. 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-133696 (continuedev continue Dev Data Logging log.ts DataLogger.logDevData information disclosure), 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-133696 (entry last updated 2026-11-20):
Affected:
- continuedev continue: versions 2.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-133696 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133696 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/441422
- https://vuldb.com/vuln/441422/cti
- https://vuldb.com/cve/CVE-2026-133696
- https://vuldb.com/submit/1051586
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-133696
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-133696"}.Affected versions
- continuedev continue2.0, 2.1.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133696 |
| Other links 4 | |
| Advisory | VulDB · Advisory #441422 |
| Advisory | VulDB · Threat intelligence #441422 |
| Advisory | VulDB · CVE-2026-133696 record |
| Advisory | VulDB · Submission #1051586 |
Questions about CVE-2026-133696
Is CVE-2026-133696 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-133696?
continue: versions 2.0, 2.1.0.
Source: cve.now feed data
Related
- CVE-2026-76072Continue CLI through 1.5.47 Incomplete Destructive Command Denylist in Headless and Auto Mode
- CVE-2026-109560Continue CLI through 1.5.47 Bash Permission Rule Bypass via Command Chaining
- CVE-2026-133694continuedev continue Mermaid Diagram Renderer ContinueGUIWebviewViewProvider.ts getSidebarContent os command injection
- CVE-2026-116109continuedev Continue MCP Server Transport ConfigHandler.ts MCPManagerSingleton.setConnections os command injection
- CVE-2026-133693continuedev continue Edit Tool editImpl.ts validateSearchAndReplaceFilepath path traversal
- CVE-2026-8770continuedev continue JSON-RPC Server lsTool.ts lsTool path traversal
No corrections so far. Something wrong on this page? Report an error.