Quick answers
- Is CVE-2026-55837 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55837 being exploited in the wild.
- How severe is CVE-2026-55837?
- Medium severity, with a CVSS score of 6.8, published 14 September 2026.
- Which products and versions are affected?
- dbt-mcp (PyPI) < 1.20.0, ECOSYSTEM:introduced=0,fixed=1.20.0.
- Is there a fix for CVE-2026-55837?
- Yes. dbt-mcp (PyPI): upgrade to 1.20.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55837 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-55837?
- Check whether you run dbt-mcp (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- dbt-mcp (PyPI): upgrade to 1.20.0 or later
pip install "dbt-mcp>=1.20.0"
Technical details
The local FastAPI OAuth helper server in dbt-mcp exposes the 'GET /dbt_platform_context' endpoint without authentication or Host header validation. After a user completes an OAuth flow, this endpoint returns the full DbtPlatformContext object, including plaintext access_token and refresh_token values. An attacker can exfiltrate these tokens through a co-located process on the same host or via a remote DNS rebinding attack targeting the victim's browser. The vulnerability is classified as CWE-306 (Missing Authentication for Critical Function) and is addressed in version 1.20.0 by adding Host validation and redacting sensitive tokens from the endpoint response.
Affected products
- dbt-labs dbt-mcp < 1.20.0
Identifiers
- CVE-2026-55837
- GHSA-jr33-mw75-7j8f
- PYSEC-2026-2443
Timeline
- 2026-06-16: disclosed
- 2026-06-19: advisory: GHSA-jr33-mw75-7j8f published