CVE-2026-73658

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% 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
Elevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: Elevated riskExposed: 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.5, Aws4FetchClient.buildUrl() and Aws4FetchClient.presign() in apps/webapp/app/v3/objectStoreClient.server.ts assign user-controlled packet keys to URL.pathname, while apps/webapp/app/routes/api.v1.packets.$.ts accepts params["*"] without rejecting dot segments and uses findResource: async () => 1 without per-resource ownership validation. WHATWG path normalization collapses .. segments before signing, allowing a caller with a valid environment API key to obtain presigned URLs for another tenant's object-store keys and read or overwrite task payloads. This issue is fixed in version 4.5.0-rc.5.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
53(Track*)
EG Risk 53/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
Severity82% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 14, 2026

Advisory Details (4)

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

trigger.dev v4.5.0-rc.5

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

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

commit db4074df54db (triggerdotdev/trigger.dev)

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

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

fix(webapp): validate packet storage paths

Patch available: triggerdotdev/trigger.dev v4.5.0-rc.5 (PR #3830 merged 2026-06-05)

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

Cross-tenant object store read and write via URL path traversal · Advisory · triggerdotdev/trigger.dev · GitHub

https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-888c-px7m-736v

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 36× 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-30 01:22 UTCEPSS rescore
  2. 2026-08-29 07:09 UTCEG score recompute
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 20:52 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 22:23 UTCEG score recompute
  7. 2026-08-26 14:47 UTCEPSS rescore
  8. 2026-08-25 23:49 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 01:21 UTCEG score recompute
  11. 2026-08-24 14:06 UTCEG score recompute
  12. 2026-08-23 04:10 UTCEG score recompute
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-22 05:40 UTCEG score recompute
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 07:11 UTCEG score recompute
  17. 2026-08-20 22:56 UTCEPSS rescore
  18. 2026-08-19 21:23 UTCEG score recompute
  19. 2026-08-19 17:04 UTCEPSS rescore
  20. 2026-08-18 22:47 UTCEG score recompute
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 00:17 UTCEG score recompute
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 01:46 UTCEG score recompute
Show 11 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 03:17 UTCEG score recompute
  4. 2026-08-16 02:15 UTCEPSS rescore
  5. 2026-08-15 04:48 UTCEG score recompute
  6. 2026-08-15 01:31 UTCEPSS rescore
  7. 2026-08-14 17:33 UTCEG score recompute
  8. 2026-08-14 16:44 UTCEG score recompute
  9. 2026-08-13 22:25 UTCEG score recompute
  10. 2026-08-13 21:32 UTCEG score recompute
  11. 2026-08-13 21:31 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73658?
CVE-2026-73658 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 4.4.2 until 4.5.0-rc.5, Aws4FetchClient.buildUrl() and Aws4FetchClient.presign() in apps/webapp/app/v3/objectStoreClient.server.ts assign user-controlled packet keys to URL.pathname, while…
When was CVE-2026-73658 disclosed?
CVE-2026-73658 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73658 actively exploited?
CVE-2026-73658 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 74.4% of all scored CVEs.
What is the CVSS score of CVE-2026-73658?
CVE-2026-73658 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-73658?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73658, 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-73658

Explore →

Is Your Infrastructure Affected by CVE-2026-73658?

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

Start Free Scan →Browse All CVEs