CVE-2026-73654
Received Received - Intake

Prototype Pollution in Trigger.dev via Metadata API

Publication date: 2026-08-13

Last updated on: 2026-08-13

Assigner: GitHub, Inc.

Description
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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-13
Last Modified
2026-08-13
Generated
2026-08-14
AI Q&A
2026-08-13
EPSS Evaluated
N/A
NVD
CVE-2026-73654
EUVD
EUVD-2026-58358

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
trigger.dev core From 3.3.8 (inc) to 4.5.6 (inc)
trigger.dev core 4.5.6
trigger.dev trigger.dev From 3.3.8 (inc) to 4.5.6 (exc)
trigger.dev trigger.dev 4.5.6

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1321 The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in Trigger.dev versions 3.3.8 to 4.5.5. It involves the PUT /api/v1/runs/:runId/metadata endpoint which allows attackers with an environment API key to manipulate Object.prototype through dangerous path segments in operation.key values. This leads to prototype pollution, corrupting shared webapp processes and affecting other tenants.

Detection Guidance

This vulnerability affects Trigger.dev versions 3.3.8 to 4.5.5. Check your installed version with npm list trigger.dev or grep the package.json file. If the version is within the vulnerable range, inspect API logs for PUT requests to /api/v1/runs/:runId/metadata with unusual operation.key values containing prototype pollution patterns like __proto__ or constructor.

Impact Analysis

An attacker could corrupt Prisma queries and Prometheus labels, break worker authentication for other tenants, and cause a full process-wide denial of service. This could disrupt services, expose data, or prevent legitimate users from accessing the platform.

Compliance Impact

This vulnerability could lead to unauthorized data access, corruption, or service disruption, potentially violating GDPR's integrity and availability principles or HIPAA's security requirements for protected health information.

Mitigation Strategies

Upgrade Trigger.dev to version 4.5.6 or later immediately. If upgrading is not possible, restrict access to the PUT /api/v1/runs/:runId/metadata endpoint by enforcing strict API key validation and rate limiting. Monitor for signs of Object.prototype pollution in application logs.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-73654. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart