---
id: "CVE-2026-94384"
kind: "vulnerability"
aliases: ["CVE-2026-94384"]
title: "AWS Connect Salesforce Lambda: missing authorization lets IAM principals bypass their permissions"
severity: "high"
cvss: 8.1
epss: 0.00317
exploited: false
status: "open"
category: "vendor"
products: []
ecosystems: []
tags: ["amazon-connect", "aws", "aws-lambda", "lab-disclosure", "salesforce", "serverless-application-repository", "vendor"]
not_affected_if: ["function-deleted-or-disabled", "version-5.26-or-later"]
published_at: "2026-09-22T00:00:00+00:00"
first_seen_at: "2026-10-24T19:43:42+00:00"
updated_at: "2026-10-25T12:38:49+00:00"
sources: [{"source": "lab", "url": "https://aws.amazon.com/security/security-bulletins/rss/2026-115-aws/", "first_seen_at": "2026-10-24T19:43:42+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-94384", "first_seen_at": "2026-10-24T20:15:27+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-94384", "first_seen_at": "2026-10-25T12:38:49+00:00"}]
---

# AWS Connect Salesforce Lambda: missing authorization lets IAM principals bypass their permissions

The sfExecuteAWSService Lambda function in Amazon Connect Salesforce Lambda, used during initial setup, passes caller-supplied parameters to privileged AWS APIs without checking authorization. Any IAM principal with lambda:InvokeFunction on that function can perform AWS operations their own IAM permissions would deny.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed AmazonConnectSalesforceLambda version in the Serverless Application Repository deployment; affected versions are `>= 5.15` and `<= 5.24.16`
- Confirm whether the `sfExecuteAWSService` function still exists in the account and who holds `lambda:InvokeFunction` on it
- Check whether the `SalesforceExecuteAWSServiceUser` parameter is set

## Fix

- Upgrade AmazonConnectSalesforceLambda to `5.26` or later
- Delete or disable the `sfExecuteAWSService` function after setup is complete
- If the function is kept, grant `lambda:InvokeFunction` only to the CTI Adapter's IAM user and set `SalesforceExecuteAWSServiceUser` to that same user; optionally deny it to all other principals with a service control policy or permission boundary

## Timeline

- 2026-10-24T19:43:42+00:00 lab https://aws.amazon.com/security/security-bulletins/rss/2026-115-aws/ — AWS: CVE-2026-94384 - Missing Authorization in AmazonConnectSalesforceLambda sfExecuteAWSService
- 2026-10-24T20:15:27+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-94384
- 2026-10-25T12:38:49+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-94384

## Documents

- [advisory] AWS: CVE-2026-94384 - Missing Authorization in AmazonConnectSalesforceLambda sfExecuteAWSService https://aws.amazon.com/security/security-bulletins/rss/2026-115-aws/

## From the sources

CVE-2026-94384 - Missing Authorization in AmazonConnectSalesforceLambda sfExecuteAWSService

### CVE-2026-94384 - Missing Authorization in AmazonConnectSalesforceLambda sfExecuteAWSService

Bulletin ID: 2026-115-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 09/22/2026 10:00 AM PDT

Description:

Amazon Connect Salesforce Lambda (AmazonConnectSalesforceLambda) is a Serverless Application Repository application that provides Lambda functions for integrating Amazon Connect with Salesforce. We identified CVE-2026-94384, a missing authorization issue in the sfExecuteAWSService Lambda function, which is used only during initial setup. The function dispatches caller-supplied parameters to privileged AWS service APIs without validating the caller's authorization. As a result, an IAM principal with lambda:InvokeFunction permission on the function can perform AWS operations that their own IAM permissions would otherwise deny.

Impacted versions: >= 5.15 AND <= 5.24.16

Resolution:

To remediate this issue, upgrade to AmazonConnectSalesforceLambda version 5.26 or later. After setup is complete, either delete or disable the sfExecuteAWSService function. If you keep the function, restrict who can invoke it: within your account, grant lambda:InvokeFunction on the function only to the single IAM user the CTI Adapter uses to call it and to no other principal (for stronger enforcement, deny it for all other principals using a service control policy or permission boundary); and set the SalesforceExecuteAWSServiceUser parameter to that same IAM user so that cross-account invocation is limited to it.

Verification:

Confirm the sfExecuteAWSService function has been deleted or disabled after setup. If you keep the function, confirm that within your account lambda:InvokeFunction on the function is granted only to the CTI Adapter's IAM user, and that the SalesforceExecuteAWSServiceUser parameter names that same user.

References:

- CVE-2026-94384
- GHSA-c9j2-qjfv-mm4p

Acknowledgement:

We would like to thank Chang Li of Xidian University for collaborating on this issue through the coordinated vulnerability disclosure process.

 Please email aws-security@amazon.com with any security questions or concerns.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_