CVE-2026-73657

MEDIUMPre-NVD 4.24.2—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.2
EG Score
4.2(medium)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity42% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Aug 13, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github, github_pr.
github_release Patch Available

trigger.dev v4.5.0-rc.4

Patch available: triggerdotdev/trigger.dev v4.5.0-rc.4 (pre-release)

https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.0-rc.4
github_commit Patch Available

commit e1950778e2f2 (triggerdotdev/trigger.dev)

Patch available: triggerdotdev/trigger.dev v4.5.0-rc.4 (contains commit e1950778e2f2)

https://github.com/triggerdotdev/trigger.dev/commit/e1950778e2f2007e2d432b8f8a8fc89531c51f19
github_pr Patch Available

feat(webapp): mollifier API mutations on buffered runs

Patch available: triggerdotdev/trigger.dev v4.5.0-rc.4 (PR #3756 merged 2026-06-01)

https://github.com/triggerdotdev/trigger.dev/pull/3756
github Patch Available🟡 PoC Available

Cross-tenant payload poisoning via packet write + replay · Advisory · triggerdotdev/trigger.dev · GitHub

https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-jx48-qfwm-xq67

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-26 21:10 UTCEG score recompute
  2. 2026-08-26 14:47 UTCEPSS rescore
  3. 2026-08-25 23:15 UTCEG score recompute
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-25 01:24 UTCEG score recompute
  6. 2026-08-22 08:06 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 10:21 UTCEG score recompute
  9. 2026-08-20 22:56 UTCEPSS rescore
  10. 2026-08-20 12:35 UTCEG score recompute
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-18 17:04 UTCEG score recompute
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 13:49 UTCEPSS rescore
  15. 2026-08-17 18:35 UTCEG score recompute
  16. 2026-08-17 17:30 UTCEG score recompute
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-16 15:41 UTCEG score recompute
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 02:15 UTCEPSS rescore
  22. 2026-08-15 17:56 UTCEG score recompute
  23. 2026-08-15 01:31 UTCEPSS rescore
  24. 2026-08-13 22:25 UTCEG score recompute
  25. 2026-08-13 21:32 UTCEG score recompute
Show 1 more
  1. 2026-08-13 21:31 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73657?
CVE-2026-73657 is a medium vulnerability published on August 13, 2026. 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…
When was CVE-2026-73657 disclosed?
CVE-2026-73657 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73657 actively exploited?
CVE-2026-73657 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.6% of all scored CVEs.
What is the CVSS score of CVE-2026-73657?
CVE-2026-73657 has a CVSS v3 base score of 4.2 (NVD).
How do I remediate CVE-2026-73657?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73657, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-73657

Explore →

Is Your Infrastructure Affected by CVE-2026-73657?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs