medium · CVSS v3 5

CVE-2026-114080

Trigger.dev before 4.5.2 contains a blind server-side request forgery vulnerability that allows authenticated project me…

Description

Trigger.dev before 4.5.2 contains a blind server-side request forgery vulnerability that allows authenticated project members to make the server send requests by setting unvalidated alert-channel webhook URLs. Attackers can create alert channels pointing to loopback, internal, or cloud metadata addresses, then trigger alerts to probe internal service reachability and send signed POST requests.

Scores

Severity
medium
CVSS v2
4
CVSS v3
5
CVSS v4
—
EPSS
—

← 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-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. This can expose run metadata and payloads from other tenants. The vulnerability is a medium severity issue.

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