Categories
CVE-2026-25650

Information Disclosure in mcp-salesforce-connector (CVE-2026-25650)

Summary

Vulnerability in mcp-salesforce-connector (CVE-2026-25650). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.1.10 or later.

Original description

The description as published by the source.

Impact

Disclosure of Salesforce OAuth bearer tokens used by the MCP.

Patches

fix applied in 0.1.10

Workarounds

Rotate any Salesforce tokens/credentials used by MCP-Salesforce.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-25650 has been found in mcp-salesforce-connector.
Risk of unauthorized operations or information disclosure.
What to do: upgrade mcp-salesforce-connector to 0.1.10 or later.
If unsure, ask your IT team or search "mcp-salesforce-connector CVE-2026-25650" on the vendor's site.

CVE-2026-25650 (mcp-salesforce-connector) — CWE-200
Patched: 0.1.10 — apply immediately
Workaround: Rotate any Salesforce tokens/credentials used by MCP-Salesforce.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in mcp-salesforce-connector.

📍 Affected scope

Check the vendor advisory for the affected versions of mcp-salesforce-connector.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.1.10.

🛡️ Workaround

Workaround: Rotate any Salesforce tokens/credentials used by MCP-Salesforce.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mcp-salesforce-connector' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'mcp-salesforce-connector' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で mcp-salesforce-connector を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    _Rotate any Salesforce tokens/credentials used by MCP-Salesforce._

    パッチが適用されるまでの応急処置として、Rotate any Salesforce tokens/credentials used by MCP-Salesforce. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade mcp-salesforce-connector to 0.1.10

    ステージング環境で 0.1.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI mcp-salesforce-connector
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.1.10"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details