ETK-2026-385Zero's internal tracking ID, independent of the CVE number.

waiting for further signalsZero needs more public information before it can validate it.

GHSA-qxpp-qjg8-x4jv ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−19dkevAttacks confirmed in the real world.
npm:trigger.dev < 4.5.2
fixed in 4.5.2
ETK-2026-385, no cve assigned
pkg:npm/trigger.dev
17d 10h 55msince last run
44mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dpublic poc+0dwaiting for further signals+1.1d
0
+5d
+10d
+15d
+20d

description

trigger.dev versions before 4.5.2 do not consistently authorize the target environment selected for dashboard task-run replays. An authenticated user who knows an environment identifier from another project or organization can create a replayed run there, potentially consuming resources and adding run-history records.

mitigation

Upgrade trigger.dev to version 4.5.2 or later. Until upgraded, restrict access to the dashboard replay feature and enforce server-side validation that replay targets belong to the source run's project or organization.

fixed in 4.5.2

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
44m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
−19d
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-02 19:31Z
    ghsa: trigger signal, started the run
  2. 2026-10-02 19:31Z

this entry in the feed

GET /api/v1/feed/ETK-2026-385

{
  "etk_id": "ETK-2026-385",
  "cve_id": null,
  "display_id": "ETK-2026-385",
  "ghsa_id": "GHSA-qxpp-qjg8-x4jv",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Cross-tenant authorization bypass in trigger.dev replay",
  "summary": "trigger.dev versions before 4.5.2 do not consistently authorize the target environment selected for dashboard task-run replays. An authenticated user who knows an environment identifier from another project or organization can create a replayed run there, potentially consuming resources and adding run-history records.",
  "mitigation": "Upgrade trigger.dev to version 4.5.2 or later. Until upgraded, restrict access to the dashboard replay feature and enforce server-side validation that replay targets belong to the source run's project or organization.",
  "vendor": "npm",
  "product": "npm:trigger.dev",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 4.5.2"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "4.5.2"
      ],
      "package_name": "trigger.dev",
      "purl": "pkg:npm/trigger.dev"
    }
  ],
  "cwes": null,
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 44.001280816666664,
  "t0_at": null,
  "signals": {
    "public_poc": {
      "at": "2026-10-02T19:31:17+00:00",
      "days": -18.558172671064813,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T08:55:03.140894+00:00",
      "url": "https://github.com/advisories/GHSA-qxpp-qjg8-x4jv"
    },
    "trigger_signal": {
      "at": "2026-10-02T19:31:17+00:00",
      "days": -18.558172671064813,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T08:55:03.140894+00:00",
      "url": "https://github.com/advisories/GHSA-qxpp-qjg8-x4jv"
    }
  }
}

published 2026-10-02 23:26Z
last change 2026-10-21 08:40Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.