How severe is GHSA-vhf8-cg2h-cg3p?

No CVSS score has been assigned to GHSA-vhf8-cg2h-cg3p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vhf8-cg2h-cg3p?

GHSA-vhf8-cg2h-cg3p affects the following packages: n8n (npm), n8n (npm). Ecosystems affected: npm.

How do I fix GHSA-vhf8-cg2h-cg3p?

Update n8n to 2.32.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vhf8-cg2h-cg3p is resolved across your whole dependency graph.

How do I detect GHSA-vhf8-cg2h-cg3p 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-vhf8-cg2h-cg3p if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-vhf8-cg2h-cg3p actively exploited in the wild?

No public exploit code has been indexed for GHSA-vhf8-cg2h-cg3p 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-vhf8-cg2h-cg3p?

GHSA-vhf8-cg2h-cg3p has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th 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-vhf8-cg2h-cg3p?

GHSA-vhf8-cg2h-cg3p is classified as Server-Side Request Forgery (SSRF) (CWE-918). 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-vhf8-cg2h-cg3p published, and has it been updated?

GHSA-vhf8-cg2h-cg3p was published on July 22, 2026 and was last updated on August 12, 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: SSRF Protection Bypass via MCP Client NodeGHSA-vhf8-cg2h-cg3p

Fix: n8n-io/n8n@f69dfc6

GHSA-vhf8-cg2h-cg3p is a Server-Side Request Forgery (SSRF) vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.

Also known asCVE-2026-72768

Published

Jul 22, 2026

Updated

Aug 12, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-vhf8-cg2h-cg3p.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs 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.

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

n8nnpm

115Kdownloads / week

Description

Impact

On an n8n instance with SSRF protection enabled, the MCP Client node sent requests to a user-supplied endpoint without routing them through that protection and without pinning the resolved address. An authenticated user who could create or edit a workflow could therefore cause the server to connect to internal or otherwise blocked hosts and read the responses back through the workflow, exposing internal services the SSRF protection was meant to protect.

Patches

The issue has been fixed in n8n versions 2.31.5 and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

Restrict n8n instance access to fully trusted users only.
Disable the MCP Client node by adding it to the NODES_EXCLUDE environment variable.
Restrict network egress from the n8n host to block access to internal and link-local address ranges at the network level.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`n8n`	≥ 2.32.0&&< 2.32.1	2.32.1`npm install n8n@2.32.1`
📦npm	`n8n`	all versions	2.31.5`npm install n8n@2.31.5`

Affected Products

1 product · 2 configurations

Application

n8nn8n

≥ 2.31.0 && < 2.31.5

1 version

2.32.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update n8n to 2.32.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vhf8-cg2h-cg3p is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

## Impact On an n8n instance with SSRF protection enabled, the MCP Client node sent requests to a user-supplied endpoint without routing them through that protection and without pinning the resolved address. An authenticated user who could create or edit a workflow could therefore cause the server to connect to internal or otherwise blocked hosts and read the responses back through the workflow, exposing internal services the SSRF protection was meant to protect. ## Patches The issue has been fixed in n8n versions 2.31.5 and 2.32.1. Users should upgrade to one of these versions or later to

O3 Security · Impact-Aware SCA

Is GHSA-vhf8-cg2h-cg3p in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works