Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-73657Published 2026-08-13

CVE-2026-73657 — triggerdotdev trigger.dev

medium

As of 2026-08-13, CVE-2026-73657 is a MEDIUM-severity vulnerability in triggerdotdev trigger.dev, CVSS v3.1 4.2, EPSS 0.1% (5.6th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-73657 as of 2026-08-13; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
4.2/10Medium
EPSS
0.1%Higher than 5.6% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
2.3/10Threadlinqs triage score
Published
CVSS v3.1 4.2 (MEDIUM) · EPSS 0.1% (higher than 5.6% of all scored CVEs) · Priority 2.3/10 · Published 2026-08-13

Last updated:

What is CVE-2026-73657?

Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. From 4.4.2 until 4.5.0-rc.4, `POST /api/v1/runs/:runParam/replay` in apps/webapp/app/routes/api.v1.runs.$runParam.replay.ts uses `prisma.taskRun.findUnique({ where: { friendlyId: runParam } })` without a runtimeEnvironmentId filter, then ReplayTaskRunService in apps/webapp/app/v3/services/replayTaskRun.server.ts replays the selected run in the victim environment. Any valid environment API key can therefore replay another tenant's run by friendlyId, consuming victim resources and repeating side effects; when `payloadType: "application/store"` is used, overrideExistingPayloadPacket() calls conditionallyImportPacket() on existingTaskRun.payload without an integrity check, so payload bytes overwritten through a separate object-store path-traversal vulnerability become attacker-controlled input to the victim task. This issue is fixed in version 4.5.0-rc.4.

The record classifies CVE-2026-73657 under weakness classes CWE-22, CWE-345, CWE-639. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 98 days ago.

Severity and exploitation probability

CVSS v3.1 base score
4.2 — MEDIUM
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L
EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 5.6% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
2.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-08-13

Is CVE-2026-73657 being exploited?

It currently carries a trending score of 31 in the Threadlinqs vulnerability feed.

Affected products and versions

  • triggerdotdev: trigger.dev

How to fix CVE-2026-73657

No vendor patch reference has been recorded for CVE-2026-73657 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-73657

No threat campaign in the Threadlinqs corpus currently references CVE-2026-73657, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references