← Back
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.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-25650** has been found in mcp-salesforce-connector.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
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
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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mcp-salesforce-connector' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `mcp-salesforce-connector` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
_Rotate any Salesforce tokens/credentials used by MCP-Salesforce._パッチが適用されるまでの応急処置として、_Rotate any Salesforce tokens/credentials used by MCP-Salesforce._ を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade mcp-salesforce-connector to 0.1.10ステージング環境で 0.1.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
mcp-salesforce-connector
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.1.10"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-25650
- advisory https://github.com/advisories/GHSA-vf6j-c56p-cq58
- package https://github.com/smn2gnt/MCP-Salesforce
- package https://pypi.org/project/mcp-salesforce-connector
- web https://github.com/smn2gnt/MCP-Salesforce/security/advisories/GHSA-vf6j-c56p-cq58
- web https://github.com/smn2gnt/MCP-Salesforce/commit/a1e3a5a786f48508d066b6d40b58201ebf9b7fd6
- web https://github.com/smn2gnt/MCP-Salesforce/releases/tag/v0.1.10