CVE-2026-736548.5HighCWE-1321

CVE-2026-73654: Trigger.dev: Prototype pollution via run metadata operations → process-wide cross-tenant DoS

triggerdotdev · trigger.dev

Affected: triggerdotdev trigger.dev · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.6%probability of exploitation in the next 30 days

50th percentile

050100

Higher than 50% of scored CVEs

8.5HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

triggerdotdev · trigger.dev>= 3.3.8, < 4.5.6

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Prototype Pollution · Deserialization and Object Injection
Vendor: triggerdotdev
Published: August 2026
Band: Unlikely (under 1%), August 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-73654 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.