Skip to main content
CVE-2026-25650VulnerabilityPublished Updated

CVE-2026-25650: smn2gnt MCP-Salesforce · Information Exposure

Affects smn2gnt MCP-SalesforceSource CVE Database V5

0

Not known to be exploited · CVSS 6.6 Medium : upgrade to 0.1.10 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
6.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.1.10
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-26.

What to do

Upgrade MCP-Salesforce and smn2gnt/MCP-Salesforce to 0.1.10.

Affected software

ProductAffectedFixed in
smn2gntMCP-SalesforceAffected
  • <0.1.10
Fixed in
  • 0.1.10
GitHubsmn2gnt/MCP-Salesforcepkg:github/smn2gnt/MCP-SalesforceOther threatsAffected
  • <0.1.10
Fixed in
  • 0.1.10

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

AI-suggested

1. Immediately upgrade the smn2gnt MCP-Salesforce Connector to version 0.1.10 or later to apply the official fix that restricts arbitrary attribute access. 2. Conduct an audit of all Salesforce integrations using the MCP-Salesforce Connector to identify and remediate any instances running vulnerable versions. 3. Rotate Salesforce authentication tokens and credentials that may have been exposed prior to patching to invalidate any compromised tokens. 4. Implement strict access controls and monitoring on Salesforce API usage to detect anomalous access patterns indicative of token misuse. 5. Employ network segmentation and firewall rules to limit exposure of MCP servers to only trusted internal systems and IP ranges. 6. Enable detailed logging and alerting on Salesforce authentication events to quickly identify unauthorized access attempts. 7. Educate development and operations teams about secure handling of authentication tokens and the importance of timely patching of integration components. 8. Review and enhance incident response plans to address potential token compromise scenarios.

Description

MCP Salesforce Connector is a Model Context Protocol (MCP) server implementation for Salesforce integration. Prior to 0.1.10, arbitrary attribute access leads to disclosure of Salesforce auth token. This vulnerability is fixed in 0.1.10.

References

Community reviews

Loading reviews…