Security readout for executives and security teams
Plain-English summary
A user holding a valid Trigger.dev API key for one project could interfere with another project's deployment by supplying its deployment identifier. The flaw can attach an unauthorized worker and change deployment state, potentially disrupting workflows or compromising deployment integrity.
Executive priority
Treat this as an immediate remediation priority for organizations operating affected Trigger.dev deployments. It has a CVSS 9.9 rating and enables authenticated cross-project interference. Prioritize version confirmation, upgrade, and review of deployment-state and worker-registration history.
Technical view
The worker-registration endpoint looked up deployments by friendlyId without restricting the query to the caller's environmentId. This cross-project authorization failure could link an attacker-controlled background worker to a victim deployment and transition it from BUILDING to DEPLOYING. The bundle maps this to CWE-639 and CWE-862.
Likely exposure
Exposure requires a reachable affected Trigger.dev deployment and a caller possessing a valid API key for any project. The bundle conflicts on affected versions: it lists versions below 4.5.2, while the description says versions before 4.5.6. Confirm scope against the vendor advisory.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires low privileges but no user interaction; successful abuse crosses project boundaries and can materially affect deployment integrity and availability.
Researcher notes
The core issue is tenant-boundary enforcement in CreateDeploymentBackgroundWorkerServiceV4.call(): workerDeployment.findFirst() lacked an environmentId predicate. Evidence supports cross-project state manipulation, but not broader compromise or active exploitation. The source bundle's 4.5.2 versus 4.5.6 version discrepancy should be resolved before final exposure reporting.
Mitigation direction
- Upgrade to Trigger.dev 4.5.6 or later, as identified by the bundle's vulnerability description.
- Confirm the corrected minimum version with the vendor advisory because the supplied version ranges conflict.
- Restrict deployment API access and rotate API keys if unauthorized use is suspected.
- Review vendor guidance for any additional containment or recovery actions.
Validation and detection
- Inventory Trigger.dev versions and identify installations potentially below 4.5.6.
- Verify deployment lookup logic scopes friendlyId queries to the authenticated environmentId.
- Review worker registrations and deployment state changes for unexpected cross-project relationships.
- Confirm unauthorized project identifiers are rejected without changing deployment state.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-73656 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H3.16GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-j6vv-pq9h-f4wjCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/triggerdotdev/trigger.dev/pull/4199CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/triggerdotdev/trigger.dev/commit/34b1a181c2a1d33a53ebab88f84b05f81fea4254CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.2CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.