CVE-2026-73658 triggerdotdev CVE debrief

Who should care

Defenders responsible for Trigger.dev deployments, particularly those using versions prior to 4.5.0-rc.5, should assess exposure and apply the fix to prevent unauthorized access to sensitive data.

Why it matters

CVE-2026-73658 is a high-severity vulnerability in Trigger.dev that allows unauthorized access to task payloads via presigned URLs. Defenders should prioritize verifying exposure and applying the fix to prevent potential data breaches or modifications.

• Potential unauthorized access to task payloads via presigned URLs.
• Possible data breaches or modifications due to insufficient access controls.
• Need for verification of exposure and application of the fix to prevent exploitation.
• Potential impact on data integrity and confidentiality.

Technical summary

The vulnerability is caused by the improper handling of user-controlled packet keys in the Aws4FetchClient.buildUrl() and Aws4FetchClient.presign() functions. This allows an attacker to obtain presigned URLs for another tenant's object-store keys, potentially enabling unauthorized access to task payloads. The issue arises from the combination of user-controlled packet keys being assigned to URL.pathname and the acceptance of params[“*”] without rejecting dot segments, which can be exploited by a caller with a valid environment API key to access or overwrite task payloads of another tenant. This vulnerability was fixed in version 4.5.0-rc.5.

Defensive priority

Defenders should prioritize verifying exposure and applying the fix, as the vulnerability allows unauthorized access to sensitive data.

Recommended defensive actions

• Verify exposure by checking if the environment uses a vulnerable version of Trigger.dev (prior to 4.5.0-rc.5) and has a valid environment API key.
• Apply the fix by updating to version 4.5.0-rc.5 or later.
• Monitor for suspicious activity related to object-store keys and task payloads.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the exact scope of affected deployments and the number of impacted users are unknown.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.