For an attacker with pre-existing access to send a signal to a workflow, the attacker can make the signal…
Historical advisory recorded 24 Oct 2026 23:17:22 UTC. Read the latest advisory.
nvd · CVE-2024-2435
PublishedFor an attacker with pre-existing access to send a signal to a workflow, the attacker can make the signal name a script that executes when a victim views that signal. The XSS is in the timeline page displaying the workflow execution details of the workflow that was sent the crafted signal. Access to send a signal to a workflow is determined by how you configured the authorizer on your server. This includes any entity with permission to directly call SignalWorkflowExecution or SignalWithStartWorkflowExecution, or any entity can deploy a worker that has access to call workflow progress APIs (specifically RespondWorkflowTaskCompleted).
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2024-2435 · CVE overview and exploitation status
nvd · CVE-2024-2435
This historical advisory does not include today's related changes. Open the latest advisory to find current connections.