CVE-2026-94384

LOWCVSS 6.4 · MEDIUM

Signal is active with 2 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

Missing authorization in Amazon amazon-connect-salesforce-lambda before 5.26 allows any IAM principal with lambda:InvokeFunction permission on the affected function to escalate privileges and perform AWS API operations that their own IAM identity is explicitly denied, via invocation of a Lambda function that dispatches caller-supplied parameters to privileged service APIs without authorization validation. To remediate this issue, we recommend upgrading to version 5.26 or later. After setup is complete, either delete or disable the sfExecuteAWSService function. If you retain the function, restrict invocation to the intended IAM user only.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-862

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 2 mentions across 1 observed day

What's happening

  • 2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d
01122Mentions · 2026-09-23: 209-23
Referenced assets2 URLs
Full discourse2 posts
  • Dark Web Intelligence@DailyDarkWeb

    ☁️🚨 AWS DISCLOSES AMAZON CONNECT–SALESFORCE PRIVILEGE-ESCALATION FLAW — LAMBDA CAN BYPASS CALLER IAM RESTRICTIONS AWS has disclosed CVE-2026-94384, a newly published authorization vulnerability in the Amazon Connect Salesforce integration that can let a lower-privileged AWS identity use a setup Lambda as a confused deputy to perform AWS API operations its own IAM policy explicitly denies. • CVE-2026-94384 — CVSS 8.1 High • Affects Amazon Connect Salesforce Lambda versions 5.15 through 5.24.16 • The vulnerable sfExecuteAWSService Lambda accepts caller-supplied parameters and dispatches them to privileged AWS service APIs without validating whether the caller is authorized for the requested operation • Any IAM principal with lambda:InvokeFunction permission on that function can potentially cross its intended IAM permission boundary • Impact includes unauthorized access to or modification of AWS resources reachable through the Lambda’s execution role • The vulnerable function is intended only for initial setup and is disabled by default — exposure therefore depends on deployment configuration • AWS recommends upgrading to version 5.26+, then deleting or disabling sfExecuteAWSService; if it must remain enabled, invocation should be restricted to the intended IAM user only • No confirmed in-the-wild exploitation or public exploit has been identified at this time ⚠️ Analyst Note: The interesting cloud-security issue is the privilege-boundary bypass. An identity can be correctly denied an AWS API action by IAM, yet still reach that action indirectly if it is allowed to invoke a more privileged Lambda that fails to re-authorize the requested operation. Organizations using the Amazon Connect–Salesforce integration should check not only package version but whether this setup function was left enabled and who currently has permission to invoke it. Original AWS security bulletin: https://aws.amazon.com/security/security-bulletins/2026-115-aws/ Original GitHub security advisory: https://github.com/amazon-connect/amazon-connect-salesforce-cti/security/advisories/GHSA-c9j2-qjfv-mm4p #AWS #AmazonConnect #Salesforce #CVE202694384 #CloudSecurity #IAM #PrivilegeEscalation #ThreatIntel #DDW #DarkWeb

    1231244.8K
    204.8K followersView on X
  • Hazem Omier@hazemomier

    CVE-2026-94384 (Connect→Salesforce Lambda): sfExecuteAWSService will run privileged AWS APIs for anyone with lambda:InvokeFunction — even if their own IAM is denied. Setup leftovers are agent-shaped risk. Upgrade to ≥5.26, then delete/disable that function or lock invoke to one principal. Don't leave "temporary" privilege bridges in the account.

    000003
    400 followersView on X

Explore more