CVE-2026-73654

HIGHPre-NVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (47th percentile of EPSS-scored CVEs). 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
Elevated
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. From 3.3.8 until 4.5.6, the PUT /api/v1/runs/:runId/metadata endpoint passes attacker-controlled operation.key values to new JSONHeroPath(operation.key).set(newMetadata, value) in packages/core/src/v3/runMetadata/operations.ts without rejecting dangerous constructor and prototype path segments. A caller with a normal environment API key can pollute Object.prototype in the shared webapp process, corrupting Prisma queries and Prometheus labels, breaking other tenants' worker authentication, and causing a process-wide denial of service. This issue is fixed in version 4.5.6.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
54
EG Risk 54/100CISA SSVC

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
Severity85% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 13, 2026

Last Modified

September 18, 2026

Advisory Details (3)

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

trigger.dev v4.5.6

Patch available: triggerdotdev/trigger.dev v4.5.6

https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.6
github_pr Patch Available

fix: security release 2026-07-08

Patch available: triggerdotdev/trigger.dev v4.5.6 (PR #4316 merged 2026-07-21)

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

Prototype pollution via run metadata operations → process-wide cross-tenant DoS (CWE-1321) · Advisory · triggerdotdev/trigger.dev · GitHub

https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-p28v-f755-9qrg

Vendor Advisories for CVE-2026-73654(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@trigger.dev/core—
  • 3.3.8 up to 4.5.6: fixed in 4.5.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 44× 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-10-05 14:36 UTCEG score recompute
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-03 19:45 UTCEG score recompute
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-02 19:51 UTCEG score recompute
  6. 2026-10-02 07:29 UTCEG score recompute
  7. 2026-10-01 19:50 UTCEPSS rescore
  8. 2026-09-30 21:44 UTCEG score recompute
  9. 2026-09-29 15:24 UTCEPSS rescore
  10. 2026-09-29 03:47 UTCEG score recompute
  11. 2026-09-28 13:52 UTCEPSS rescore
  12. 2026-09-28 00:38 UTCEG score recompute
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-27 09:42 UTCEG score recompute
  15. 2026-09-26 15:59 UTCEPSS rescore
  16. 2026-09-25 03:30 UTCEG score recompute
  17. 2026-09-24 04:09 UTCEG score recompute
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-23 03:08 UTCEG score recompute
  20. 2026-09-22 02:26 UTCEG score recompute
  21. 2026-09-21 21:09 UTCEPSS rescore
  22. 2026-09-21 01:06 UTCEG score recompute
  23. 2026-09-20 20:16 UTCEPSS rescore
  24. 2026-09-19 23:34 UTCEG score recompute
  25. 2026-09-18 20:24 UTCEG score recompute
Show 69 more
  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 00:38 UTCEG score recompute
  3. 2026-09-16 23:58 UTCEG score recompute
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 12:09 UTCEG score recompute
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-13 20:53 UTCEG score recompute
  9. 2026-09-12 20:13 UTCEG score recompute
  10. 2026-09-12 15:02 UTCEPSS rescore
  11. 2026-09-11 19:13 UTCEG score recompute
  12. 2026-09-10 18:33 UTCEG score recompute
  13. 2026-09-10 09:35 UTCEPSS rescore
  14. 2026-09-09 04:53 UTCEG score recompute
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-07 16:29 UTCEG score recompute
  17. 2026-09-06 20:41 UTCEG score recompute
  18. 2026-09-06 13:48 UTCEPSS rescore
  19. 2026-09-05 19:58 UTCEG score recompute
  20. 2026-09-04 19:17 UTCEG score recompute
  21. 2026-09-04 06:14 UTCEG score recompute
  22. 2026-09-04 05:07 UTCEPSS rescore
  23. 2026-09-03 01:25 UTCEG score recompute
  24. 2026-09-02 14:12 UTCEPSS rescore
  25. 2026-09-01 23:37 UTCEG score recompute
  26. 2026-09-01 13:54 UTCEPSS rescore
  27. 2026-09-01 11:17 UTCEG score recompute
  28. 2026-09-01 04:40 UTCEPSS rescore
  29. 2026-09-01 04:40 UTCEPSS rescore
  30. 2026-08-30 21:04 UTCEG score recompute
  31. 2026-08-30 19:18 UTCEPSS rescore
  32. 2026-08-30 19:17 UTCEPSS rescore
  33. 2026-08-30 08:44 UTCEG score recompute
  34. 2026-08-30 01:22 UTCEPSS rescore
  35. 2026-08-29 07:14 UTCEG score recompute
  36. 2026-08-28 21:42 UTCEPSS rescore
  37. 2026-08-28 02:28 UTCEG score recompute
  38. 2026-08-27 14:25 UTCEPSS rescore
  39. 2026-08-27 01:48 UTCEG score recompute
  40. 2026-08-26 14:47 UTCEPSS rescore
  41. 2026-08-26 01:00 UTCEG score recompute
  42. 2026-08-25 13:49 UTCEPSS rescore
  43. 2026-08-25 00:20 UTCEG score recompute
  44. 2026-08-24 12:00 UTCEG score recompute
  45. 2026-08-23 11:20 UTCEG score recompute
  46. 2026-08-23 00:19 UTCEPSS rescore
  47. 2026-08-22 10:40 UTCEG score recompute
  48. 2026-08-21 23:49 UTCEPSS rescore
  49. 2026-08-21 10:00 UTCEG score recompute
  50. 2026-08-20 22:56 UTCEPSS rescore
  51. 2026-08-19 21:00 UTCEG score recompute
  52. 2026-08-19 17:04 UTCEPSS rescore
  53. 2026-08-18 20:20 UTCEG score recompute
  54. 2026-08-18 13:49 UTCEPSS rescore
  55. 2026-08-18 13:49 UTCEPSS rescore
  56. 2026-08-17 19:38 UTCEG score recompute
  57. 2026-08-17 13:47 UTCEPSS rescore
  58. 2026-08-16 18:58 UTCEG score recompute
  59. 2026-08-16 14:56 UTCEPSS rescore
  60. 2026-08-16 14:56 UTCEPSS rescore
  61. 2026-08-16 06:33 UTCEG score recompute
  62. 2026-08-16 02:15 UTCEPSS rescore
  63. 2026-08-15 05:54 UTCEG score recompute
  64. 2026-08-15 01:31 UTCEPSS rescore
  65. 2026-08-14 17:34 UTCEG score recompute
  66. 2026-08-14 16:44 UTCEG score recompute
  67. 2026-08-13 20:20 UTCEG score recompute
  68. 2026-08-13 19:47 UTCEG score recompute
  69. 2026-08-13 19:46 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73654?
CVE-2026-73654 is a high vulnerability published on August 13, 2026. Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. From 3.3.8 until 4.5.6, the PUT /api/v1/runs/:runId/metadata endpoint passes attacker-controlled operation.key values to new JSONHeroPath(operation.key).set(newMetadata, value) in…
When was CVE-2026-73654 disclosed?
CVE-2026-73654 was first published on August 13, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73654 actively exploited?
CVE-2026-73654 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73654?
CVE-2026-73654 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73654?
A fix for CVE-2026-73654 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73654 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73654

Explore →

Is Your Infrastructure Affected by CVE-2026-73654?

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

Book a Demo →Browse All CVEs