A significant vulnerability was disclosed by AWS in its Amazon Connect Salesforce Lambda application, affecting the sfExecuteAWSService Lambda function across versions 5.15 through 5.24.16 This article explores vulnerability disclosed aws. . This flaw, tracked as CVE-2026-94384, allows attackers to perform unauthorized cloud actions beyond their assigned IAM permissions.
An IAM principal requires only the lambda: InvokeFunction permission for the vulnerable function to potentially execute AWS operations that their individual IAM policy would normally block. An attacker who gains access to an IAM identity with permission to invoke the function can abuse the issue to access AWS services, modify cloud resources, or carry out actions allowed by the Lambda execution role.
This issue is particularly concerning in environments where Lambda invocation permissions are broadly granted to developers, automation accounts, third-party integrations, or other IAM principals. AWS has released AmazonConnectSalesforceLambda version 5.26 to address this concern. Organizations using impacted versions should upgrade immediately and review whether the sfExecuteAWSService function remains necessary after the Amazon Connect and Salesforce integration is configured.
To ensure data safety, teams should review IAM policies, Lambda resource policies, execution roles, CloudTrail logs, and cross-account trust settings for any unauthorized activity. This action has reduced SOC alert investigations by 21 minutes, enhancing response times with integrated IOC context: Integrate TI Lookup into your SOC.












