Skip to main content
Menu
CVEs

continue information disclosure in config resolution

CVE-2026-133697Published , updated

2.4LowCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

Continuedev's Continue product contains an information disclosure flaw in its config resolution component, where manipulating the Name argument of the resolveFQSNs function can expose data. An attacker needs local access to the system and some low-level login, and the victim must take an action to trigger it.

Written by a model

Original description

A vulnerability has been found in continuedev continue up to 2.1.0. This vulnerability affects the function LocalPlatformClient.resolveFQSNs of the file core/config/yaml/LocalPlatformClient.ts of the component Config Resolution. Such manipulation of the argument Name leads to information disclosure. Local access is required to approach this attack. 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-133697 (continuedev continue Config Resolution LocalPlatformClient.ts LocalPlatformClient.resolveFQSNs 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-133697 (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-133697 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133697 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/441423
- https://vuldb.com/vuln/441423/cti
- https://vuldb.com/cve/CVE-2026-133697
- https://vuldb.com/submit/1051592
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-133697
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-133697"}.

Affected versions

cve.now Index

7Pof 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
  • Severity2.4/10CVSS 2.4
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 29 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-133697
RecordNVD · CVE-2026-133697
Other links 4
AdvisoryVulDB · Advisory #441423
AdvisoryVulDB · Threat intelligence #441423
AdvisoryVulDB · CVE-2026-133697 record
AdvisoryVulDB · Submission #1051592

Questions about CVE-2026-133697

Is CVE-2026-133697 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-133697?

continue: versions 2.0, 2.1.0.

Source: cve.now feed data

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