Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-25650: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in smn2gnt MCP-Salesforce

0
Medium
VulnerabilityCVE-2026-25650cvecve-2026-25650cwe-200
Published: Fri Feb 06 2026 (02/06/2026, 18:53:58 UTC)
Source: CVE Database V5
Vendor/Project: smn2gnt
Product: MCP-Salesforce

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/14/2026, 12:11:19 UTC

Technical Analysis

CVE-2026-25650 is a vulnerability classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) affecting the smn2gnt MCP-Salesforce Connector, a Model Context Protocol server implementation designed for Salesforce integration. Versions prior to 0.1.10 improperly handle attribute access, allowing attackers to retrieve arbitrary attributes without authentication. This flaw specifically exposes the Salesforce authentication token, a critical credential that grants access to Salesforce resources. The vulnerability can be exploited remotely over the network without any privileges or user interaction, making it highly accessible to attackers. The exposure of the auth token compromises confidentiality, enabling unauthorized access to Salesforce accounts and potentially sensitive business data. The vulnerability was publicly disclosed and assigned a CVSS 4.0 score of 6.6, indicating a medium severity level. The vendor addressed the issue in version 0.1.10 by restricting arbitrary attribute access and securing token handling. No public exploit code or active exploitation has been reported to date. Organizations using affected versions should upgrade promptly to prevent unauthorized data disclosure and potential downstream impacts on Salesforce-integrated workflows.

Potential Impact

For European organizations, the exposure of Salesforce authentication tokens can lead to unauthorized access to critical business data, customer information, and internal workflows managed via Salesforce. This can result in data breaches, regulatory non-compliance (e.g., GDPR violations), reputational damage, and operational disruptions. Since Salesforce is widely used across various sectors including finance, healthcare, retail, and public services in Europe, the impact can be significant. Attackers gaining access to Salesforce environments could manipulate sales data, extract sensitive customer records, or disrupt business processes. The vulnerability’s ease of exploitation and lack of required authentication increase the risk profile, especially for organizations that have not updated the MCP-Salesforce Connector. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, emphasizing the need for proactive mitigation.

Mitigation Recommendations

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.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-04T05:15:41.792Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69863dc0f9fa50a62f292946

Added to database: 2/6/2026, 7:15:12 PM

Last enriched: 2/14/2026, 12:11:19 PM

Last updated: 3/24/2026, 12:43:33 AM

Views: 99

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses