How severe is GHSA-9g95-qf3f-ggrw?

No CVSS score has been assigned to GHSA-9g95-qf3f-ggrw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9g95-qf3f-ggrw?

GHSA-9g95-qf3f-ggrw affects the following packages: n8n (npm), n8n (npm). Ecosystems affected: npm.

How do I fix GHSA-9g95-qf3f-ggrw?

Update n8n to 2.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9g95-qf3f-ggrw is resolved across your whole dependency graph.

How do I detect GHSA-9g95-qf3f-ggrw 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-9g95-qf3f-ggrw if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-9g95-qf3f-ggrw actively exploited in the wild?

No public exploit code has been indexed for GHSA-9g95-qf3f-ggrw 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-9g95-qf3f-ggrw?

GHSA-9g95-qf3f-ggrw has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 50th 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-9g95-qf3f-ggrw?

GHSA-9g95-qf3f-ggrw is classified as OS Command Injection (CWE-78). 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-9g95-qf3f-ggrw published, and has it been updated?

GHSA-9g95-qf3f-ggrw was published on February 4, 2026 and was last updated on February 4, 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 has OS Command Injection in Git NodeGHSA-9g95-qf3f-ggrw

GHSA-9g95-qf3f-ggrw is a OS Command Injection vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.

Also known asCVE-2026-25053

Published

Feb 4, 2026

Updated

Feb 4, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 9, 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-9g95-qf3f-ggrw.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% 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.

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

n8nnpm

154Kdownloads / week

Description

Impact

Vulnerabilities in the Git node allowed authenticated users with permission to create or modify workflows to execute arbitrary system commands or read arbitrary files on the n8n host.

Patches

The issue has been fixed in n8n versions 2.5.0, and 1.123.10. Users should upgrade to this version or later to remediate the vulnerability.

Workarounds

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

Limit workflow creation and editing permissions to fully trusted users only.
Restrict or disable access to the Git node if not essential for operations.
Deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation.

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

Resources

n8n Documentation — Blocking nodes — how to globally disable specific nodes

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:C/C:H/I:H/A:H

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`n8n`	≥ 2.0.0&&< 2.5.0	2.5.0`npm install n8n@2.5.0`
📦npm	`n8n`	all versions	1.123.10`npm install n8n@1.123.10`

Affected Products

1 product · 2 configurations

Application

n8nn8n

≥ 2.0.0 && < 2.5.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 2.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9g95-qf3f-ggrw is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

## Impact Vulnerabilities in the Git node allowed authenticated users with permission to create or modify workflows to execute arbitrary system commands or read arbitrary files on the n8n host. ## Patches The issue has been fixed in n8n versions 2.5.0, and 1.123.10. Users should upgrade to this version or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Limit workflow creation and editing permissions to fully trusted users only. - Restrict or disable access to the Git node

O3 Security · Impact-Aware SCA

Is GHSA-9g95-qf3f-ggrw in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

n8n has OS Command Injection in Git NodeGHSA-9g95-qf3f-ggrw

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Workarounds

Resources

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-9g95-qf3f-ggrw in your dependencies?