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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H

EPSS

• CVE-2026-73654: 0.62% estimated exploitation activity in the next 30 days; percentile 49.77 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The run-metadata update endpoint PUT /api/v1/runs/:runId/metadata applies client-supplied "operations" by passing the attacker-controlled operation.key straight into new JSONHeroPath(operation.key).set(newMetadata, value) (packages/core/src/v3/runMetadata/operations.ts:22-23), with no prototype-pollution guard (@jsonhero/path@^1.0.21 does not reject proto/constructor/prototype). A request with key: "$.proto.polluted" sets Object.prototype.polluted in the webapp process. Because every plain object then inherits that property, it corrupts unrelated code process-wide and across tenants — including Prisma query building and the Prometheus metrics client — causing query failures, broken authentication for other tenants' workers, and an uncaughtException (denial of service). Only a normal, low-privilege environment API key is required (one request). Severity A single request from any holder of a normal environment API key contaminates Object.prototype in the shared webapp process,…

Published by the source

13 Aug 2026, 20:54 UTC

Last modified by the source

13 Aug 2026, 20:54 UTC

Source last checked

26 Oct 2026, 13:01 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-p28v-f755-9qrg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73654

Advisory: Trigger.dev: Prototype pollution via run metadata operations → process-wide cross-tenant DoS
IDs: CVE-2026-73654, GHSA-p28v-f755-9qrg
Record: https://patchnext.com/advisories/cve-2026-73654 (revision 1, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @trigger.dev/core 4.5.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @trigger.dev/core: affected >= 3.3.8, <= 4.5.5; fixed in 4.5.6

## Suggested inspection (read-only)
- `npm ls @trigger.dev/core --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @trigger.dev/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p28v-f755-9qrg (GitHub-reviewed advisory GHSA-p28v-f755-9qrg lists affected ranges: npm @trigger.dev/core >=3.3.8 <=4.5.5)

Commands are suggestions: review each one before running it.