CVE-2026-114069 triggerdotdev CVE debrief

Who should care

Defenders responsible for Trigger.dev installations, especially those with untrusted or internet-exposed instances, should assess exposure and prioritize remediation. Security teams and administrators of affected systems should verify the vulnerability's presence, review existing secrets and tokens, and monitor for suspicious activity.

Why it matters

CVE-2026-114069 is a high-severity vulnerability in Trigger.dev that allows attackers to obtain root secrets and plaintext secrets, potentially leading to unauthorized task triggering and admin JWT creation. Defenders should prioritize verifying exposure, especially for untrusted or internet-exposed instances, and upgrade to version 4.6.0 or later. The vulnerability's impact and exploitation are not explicitly stated in the corpus, requiring verification from official sources.

• Potential unauthorized access to sensitive secrets and tokens.
• Possible exploitation of Trigger.dev instances for unauthorized task triggering.
• Risk of admin JWT creation for unauthorized access.
• Need for verification of exposure and remediation due to limited information on exploitation.

Technical summary

The vulnerability exists in the GET /api/v1/projects/:projectRef/envvars endpoint of Trigger.dev, where an improper authorization issue allows attackers with a restricted read:envvars key to obtain the root secret and plaintext secrets. This could lead to unauthorized task triggering and admin JWT creation. The vulnerability affects Trigger.dev versions before 4.6.0. To mitigate this vulnerability, defenders should prioritize verifying exposure of Trigger.dev installations, especially those with untrusted or internet-exposed instances, and upgrade to version 4.6.0 or later. Monitoring for suspicious activity related to envvars API access and reviewing existing secrets and tokens is also recommended. A thorough

Defensive priority

Defenders should prioritize verifying exposure of Trigger.dev installations, especially those with untrusted or internet-exposed instances, and upgrade to version 4.6.0 or later. Monitoring for suspicious activity related to envvars API access and reviewing existing secrets and tokens is also recommended.

Recommended defensive actions

• Verify Trigger.dev installations for exposure, especially those with untrusted or internet-exposed instances.
• Upgrade Trigger.dev to version 4.6.0 or later.
• Monitor for suspicious activity related to envvars API access.
• Review existing secrets and tokens for potential compromise.
• Perform a thorough review of the envvars API endpoint configuration.
• Implement additional logging and monitoring for the envvars API endpoint.
• Conduct a security audit to identify potential vulnerabilities in Trigger.dev deployments.

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to vendor advisories. However, the corpus does not provide explicit information on exploitation or victim impact.

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.