Vulnerability
Published 2026-09-24
Updated 2026-10-31
Verified 2026-10-31

SalesBleed (Zenity): Salesforce Agentforce Trusted URLs / Slack — 0-click data exfiltration + agent phishing (all fixes confirmed 21 Sep)

Zenity Labs published two SalesBleed write-ups on 24 September 2026 about Salesforce Agentforce. In the first, an indirect prompt injection entered through a public Web-to-Lead form and led to 0-click data exfiltration; Zenity says it bypassed Salesforce's Trusted URLs mechanism, a redaction layer built to strip untrusted URLs out of agent responses, by combining two edge cases in how URLs are identified. In the second, Zenity describes hijacking Agentforce in Slack for anonymous phishing attacks through identity impersonation.

Zenity reported the findings to Salesforce on 1 June 2026. It confirmed Salesforce's fix for the reported Trusted URLs bypass on 19 August, confirmed on 20 August that the Reply to a Slack Thread action now included correct attribution to the invoking user, and says all fixes were confirmed and tested on 21 September 2026. (source: Zenity Labs)

Correction (31 Oct 2026): replaced SecurityWeek, which this desk cannot read, and a link to Cyber Security News's home page with Zenity Labs' own write-ups, removed details that only SecurityWeek gave, and moved the card date from 25 to 24 September 2026, the date of Zenity's posts. (source: Zenity Labs)

Product
Salesforce Agentforce (Trusted URLs; Agentforce–Slack integration; Web-to-Lead)
Versions
Reported to Salesforce 1 Jun 2026; all fixes confirmed and tested 21 Sep 2026 (Zenity). Review Trusted URLs allowlists and Agentforce Slack actions.
Exploited in Australia?
unknown
Patch to
Confirm Salesforce’s Agentforce fixes are live on your org; tighten Web-to-Lead intake and Agentforce Trusted URLs; restrict and monitor agent write actions in Slack; hunt for anomalous agent-originated Slack messages.

ai cloud identity