How severe is GHSA-2xcx-75h9-vr9h?

No CVSS score has been assigned to GHSA-2xcx-75h9-vr9h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2xcx-75h9-vr9h?

GHSA-2xcx-75h9-vr9h affects the following packages: n8n (npm). Ecosystems affected: npm.

How do I fix GHSA-2xcx-75h9-vr9h?

Update n8n to 1.121.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2xcx-75h9-vr9h is resolved across your whole dependency graph.

How do I detect GHSA-2xcx-75h9-vr9h in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2xcx-75h9-vr9h 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.

Is GHSA-2xcx-75h9-vr9h actively exploited in the wild?

No public exploit code has been indexed for GHSA-2xcx-75h9-vr9h 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-2xcx-75h9-vr9h?

GHSA-2xcx-75h9-vr9h has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 23th 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-2xcx-75h9-vr9h?

GHSA-2xcx-75h9-vr9h is classified as Improper Input Validation (CWE-20), CWE-522 (CWE-522). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2xcx-75h9-vr9h published, and has it been updated?

GHSA-2xcx-75h9-vr9h was published on February 4, 2026 and was last updated on February 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

n8n's domain allowlist bypass enables credential exfiltrationGHSA-2xcx-75h9-vr9h

GHSA-2xcx-75h9-vr9h is a Improper Input Validation vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.

Also known asCVE-2026-25631

Published

Feb 4, 2026

Updated

Feb 19, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2xcx-75h9-vr9h.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk-0.00%

Lower risk than most CVEs23th percentile — riskier than 23% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

36other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

n8nnpm

152Kdownloads / week

Description

Impact

A vulnerability in the HTTP Request node's credential domain validation allowed an authenticated attacker to send requests with credentials to unintended domains, potentially leading to credential exfiltration.

This only might affect user who have credentials that use wildcard domain patterns (e.g., *.example.com) in the "Allowed domains" setting.

Patches

This issue is fixed in version 1.121.0 and later. All users are strongly encouraged to upgrade.

Workarounds

Until projects can upgrade:

Replace wildcard domain patterns with explicit domain listings in HTTP Request credentials
Review and restrict workflow creation/modification permissions to trusted users only
Audit existing workflows using HTTP Request nodes with domain-restricted credentials

n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backward compatibility.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`n8n`	all versions	1.121.0`npm install n8n@1.121.0`

Affected Products

1 product · 1 configurations

Application

n8nn8n

< 1.121.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update n8n to 1.121.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2xcx-75h9-vr9h 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.

Frequently Asked Questions

## Impact A vulnerability in the HTTP Request node's credential domain validation allowed an authenticated attacker to send requests with credentials to unintended domains, potentially leading to credential exfiltration. This only might affect user who have credentials that use wildcard domain patterns (e.g., `*.example.com`) in the "Allowed domains" setting. ## Patches This issue is fixed in version 1.121.0 and later. All users are strongly encouraged to upgrade. ## Workarounds Until projects can upgrade: - Replace wildcard domain patterns with explicit domain listings in HTTP Request c

O3 Security · Impact-Aware SCA

Is GHSA-2xcx-75h9-vr9h in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

n8n's domain allowlist bypass enables credential exfiltrationGHSA-2xcx-75h9-vr9h

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Workarounds

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-2xcx-75h9-vr9h in your dependencies?