Skip to main content
VulnerabilityPublished Updated

CVE-2026-55837: dbt-mcp · Information Exposure

Affects dbt-mcpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 1.20.0 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.20.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade dbt-mcp and dbt-labs/dbt-mcp to 1.20.0.

Affected software

ProductAffectedFixed in
dbt-labsdbt-mcpAffected
  • <1.20.0
Fixed in
  • 1.20.0
GitHubdbt-labs/dbt-mcppkg:github/dbt-labs/dbt-mcpOther threatsAffected
  • <1.20.0
Fixed in
  • 1.20.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in dbt-mcp version 1.20.0. Users should upgrade to version 1.20.0 or later to remediate this issue. Until upgrading, restricting access to localhost:6785 and implementing network-level protections against DNS rebinding attacks may reduce risk, but the definitive fix is to apply the official update.

Description

dbt-mcp is a Model Context Protocol server for interacting with dbt. Prior to 1.20.0, the local OAuth helper in src/dbt_mcp/oauth/fastapi_app.py exposes GET /dbt_platform_context without authentication or Host validation after a user completes the dbt Platform OAuth flow. The endpoint returns the full DbtPlatformContext, including access_token and refresh_token values persisted by the context manager, to any process that can reach 127.0.0.1:6785. The absence of TrustedHostMiddleware allows a remote attacker to use DNS rebinding against a victim's browser because the helper accepts arbitrary Host headers, while a co-located process can request the endpoint directly. The stolen tokens provide immediate dbt Platform API access as the victim and persistent access through the refresh token, allowing access to or modification of projects, jobs, environment secrets, and related account data. This issue is fixed in version 1.20.0.

References

Community reviews

Loading reviews…