CVE Intelligence
High Access control

CVE-2026-114066 — Trigger.dev before 4.7.0 Missing Authorization via Batch parentRunId Waitpoints

Trigger.dev before 4.7.0 contains a missing authorization vulnerability that allows holders of unrestricted environment API keys to block runs they do not own by supplying a foreign parentRunId to batch-creation endpoints. Attackers can send requests to POST /api/v3/batches or POST /api/v2/tasks/batch with resumeParentOnCompletion to suspend, indefinitely block, or inject errors into production or cross-organization runs.

Published Oct 20, 2026 · Updated Oct 20, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.28%
ahead of 19% of scored CVEs · Oct 21, 2026
Affects
Triggerdotdev
Trigger.dev
CVSS base
8.1
High · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Triggerdotdev Trigger.dev).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Triggerdotdev Trigger.dev < 4.7.0 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.2 CVSS 4.0 High — — disclosure@vulncheck.com via NIST National Vulnerability Database
7.2 CVSS 4.0 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
8.1 CVSS 3.1 High 2.8 5.2 disclosure@vulncheck.com via NIST National Vulnerability Database
8.1 CVSS 3.1 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-639 · Authorization Bypass Through User-Controlled Key (IDOR)

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Audit administrative actions and access to resources outside each user’s normal pattern.
web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · triggerdotdev/trigger.dev
    Oct 20, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 20, 2026
  • CVSS changed · 8.1
    Oct 20, 2026 · NIST National Vulnerability Database
  • Source status changed · → Deferred
    Oct 20, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 20, 2026 · Alertas do Telegram
  • CVE published
    Oct 20, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 20, 2026 – Oct 20, 2026
  • 1× Official description updated · Oct 20, 2026 – Oct 20, 2026

References

2 on the record

Elsewhere on this site

Triggerdotdev
every CVE for this vendor
Access control
same class
CWE-639
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-114093 Trigger.dev before 4.5.6 Cross-Site Request Forgery via /logout Endpoint 1d
  • CVE-2026-114092 Trigger.dev before 4.5.0 Missing Authentication in Dashboard Run Replay Action 1d
  • CVE-2026-114091 Trigger.dev before 4.5.0 Cross-Tenant Run Payload Disclosure via API Replay Route 1d
  • CVE-2026-114087 Trigger.dev before 4.5.6 Authentication Bypass via Hardcoded Default Secrets 1d
  • CVE-2026-114089 Trigger.dev before 4.5.2 CLI Auth-Code Phishing Leading to PAT Takeover 1d
  • CVE-2026-114086 Trigger.dev before 4.5.5 Unauthenticated Realtime Stream Data Injection via Streams Endpoint 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-114066 is "Trigger.dev before 4.7.0 Missing Authorization via Batch parentRunId Waitpoints", rated High. It affects Trigger.dev (Triggerdotdev); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.1 describes technical severity. EPSS 0.28% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.