How severe is GHSA-v2x8-97xq-8xrr?

GHSA-v2x8-97xq-8xrr has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-v2x8-97xq-8xrr?

GHSA-v2x8-97xq-8xrr affects the following packages: @n8n/n8n-nodes-langchain (npm). Ecosystems affected: npm.

How do I fix GHSA-v2x8-97xq-8xrr?

Update @n8n/n8n-nodes-langchain to 1.107.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v2x8-97xq-8xrr is resolved across your whole dependency graph.

How do I detect GHSA-v2x8-97xq-8xrr in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @n8n/n8n-nodes-langchain. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-v2x8-97xq-8xrr if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-v2x8-97xq-8xrr?

O3 pinpoints whether GHSA-v2x8-97xq-8xrr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-v2x8-97xq-8xrr actively exploited in the wild?

No public exploit code has been indexed for GHSA-v2x8-97xq-8xrr 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-v2x8-97xq-8xrr?

GHSA-v2x8-97xq-8xrr has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 42th 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.

When was GHSA-v2x8-97xq-8xrr published, and has it been updated?

GHSA-v2x8-97xq-8xrr was published on September 8, 2025 and was last updated on September 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-v2x8-97xq-8xrr: N8N's Chat Trigger component is vulnerable…

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk42th percentile+0.43%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@n8n/n8n-nodes-langchainnpm

55Kdownloads / week

Description

An arbitrary file upload vulnerability in the Chat Trigger component of N8N v1.95.3, v1.100.1, and v1.101.1 allows attackers to execute arbitrary code via uploading a crafted HTML file.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@n8n/n8n-nodes-langchain`	all versions	1.107.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @n8n/n8n-nodes-langchain. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @n8n/n8n-nodes-langchain to 1.107.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v2x8-97xq-8xrr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-v2x8-97xq-8xrr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-v2x8-97xq-8xrr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An arbitrary file upload vulnerability in the Chat Trigger component of N8N v1.95.3, v1.100.1, and v1.101.1 allows attackers to execute arbitrary code via uploading a crafted HTML file.

O3 Security · Impact-Aware SCA

Is GHSA-v2x8-97xq-8xrr in your dependencies?

O3 detects GHSA-v2x8-97xq-8xrr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-v2x8-97xq-8xrr