How severe is GHSA-p6j2-2fjh-vc8v?

No CVSS score has been assigned to GHSA-p6j2-2fjh-vc8v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p6j2-2fjh-vc8v?

Affected package information for GHSA-p6j2-2fjh-vc8v is not yet fully mapped. Check the official advisory links for details.

How do I fix GHSA-p6j2-2fjh-vc8v?

Upgrade the affected component to the fixed release for GHSA-p6j2-2fjh-vc8v, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect GHSA-p6j2-2fjh-vc8v in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate GHSA-p6j2-2fjh-vc8v if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is GHSA-p6j2-2fjh-vc8v actively exploited in the wild?

No public exploit code has been indexed for GHSA-p6j2-2fjh-vc8v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-p6j2-2fjh-vc8v?

GHSA-p6j2-2fjh-vc8v has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-p6j2-2fjh-vc8v?

GHSA-p6j2-2fjh-vc8v is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-p6j2-2fjh-vc8v published, and has it been updated?

GHSA-p6j2-2fjh-vc8v was published on October 21, 2026 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Trigger.dev before 4.5.6 SQL Injection via tags in Realtime…

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

Trigger.dev before 4.5.6 contains an SQL injection vulnerability in the /realtime/v1/runs endpoint, which concatenates the unescaped tags query parameter into the ElectricSQL shape where clause and defeats the runtimeEnvironmentId tenant guard. Authenticated attackers holding any project API key with read:runs scope can append boolean conditions to stream TaskRun records, including payloads and metadata, from every organization on the same self-hosted instance.

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for GHSA-p6j2-2fjh-vc8v, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

Trigger.dev before 4.5.6 contains an SQL injection vulnerability in the /realtime/v1/runs endpoint, which concatenates the unescaped tags query parameter into the ElectricSQL shape where clause and defeats the runtimeEnvironmentId tenant guard. Authenticated attackers holding any project API key with read:runs scope can append boolean conditions to stream TaskRun records, including payloads and metadata, from every organization on the same self-hosted instance.

O3 Security · Impact-Aware SCA

Is GHSA-p6j2-2fjh-vc8v in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

Trigger.dev before 4.5.6 SQL Injection via tags in Realtime Runs APIGHSA-p6j2-2fjh-vc8v

EPSS Exploitation Probability

Description

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-p6j2-2fjh-vc8v in your dependencies?