medium · CVSS v3 6.5

CVE-2026-114065

Trigger.dev versions prior to 4.7.3 allow authenticated users to bypass tenant isolation by using placeholder table syntax in the query API.

Overview

Trigger.dev versions prior to 4.7.3 allow authenticated users to bypass tenant isolation by using placeholder table syntax in the query API. This can expose run metadata and payloads from other tenants. The vulnerability is a medium severity issue.

Description

Trigger.dev before 4.7.3 contains a tenant filtering bypass vulnerability that allows authenticated users to read other tenants' data by using placeholder table syntax in POST /api/v1/query. Attackers can submit queries with FROM {database.table} expressions, including within subqueries, to skip table allowlist and tenant filters and expose run metadata and payloads.

Impact

Confidentiality: unauthorized disclosure of tenant data. Integrity: potential manipulation of run metadata. Availability: not directly impacted. Defenders: organizations using Trigger.dev for multi-tenant workloads.

Remediation

Upgrade to Trigger.dev 4.7.3 or later. If upgrade not possible, restrict API access to trusted users, enforce strict tenant isolation, monitor query logs for placeholder syntax, and apply firewall rules to block unauthorized query patterns.

Risk context

The vulnerability has a medium CVSS v3 score of 6.5. No EPSS data available. While not critical, it warrants timely patching to prevent data leakage.

Affected products

  • Trigger.dev API

Scores

Severity
medium
CVSS v2
6.8
CVSS v3
6.5
CVSS v4
—
EPSS
—

tenant-isolation multi-tenant API data-leak medium Trigger.dev

← All CVEs

Related CVEs

medium

CVE-2026-114088

Trigger.dev before 4.5.4 contains a hardcoded default secret vulnerability in the /coordinator Socket.IO namespace that allows unauthenticated attackers to connect using the published coordinator-secret value. Attackers can emit READY_FOR_EXECUTION to retrieve decrypted run environment variables or send TASK_RUN_FAILED_TO_RUN and similar events to tamper with arbitrary runs.

View analysis

medium

CVE-2026-114064

Snipe-IT before 8.7.0 contains a server‑side request forgery in the webhook testing feature. Super‑admin users can use it to probe internal network addresses, including loopback and RFC1918 ranges. This allows mapping of internal hosts and open ports.

View analysis

medium

CVE-2026-114067

Trigger.dev versions 4.5.0 through 4.6.1 have an improper authorization flaw in the PUT snapshot-url session endpoint. Public session tokens can retrieve presigned S3 write URLs, allowing users to overwrite durable chat snapshots and forge conversation history. This can mislead agents and compromise data integrity.

View analysis

medium

CVE-2026-114070

Trigger.dev 4.5.0 before 4.6.0 contains an information disclosure vulnerability in the Dashboard Agent input proxy that stores a delegated user-actor token in browser-readable session input records. Attackers holding a chat's public session token can read the in records endpoint to recover the token from payload.metadata.userActorToken and replay it for environment JWT exchange.

View analysis