How severe is GHSA-5xrp-6693-jjx9?

GHSA-5xrp-6693-jjx9 has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-5xrp-6693-jjx9?

GHSA-5xrp-6693-jjx9 affects the following packages: n8n (npm), n8n (npm), n8n (npm). Ecosystems affected: npm.

How do I fix GHSA-5xrp-6693-jjx9?

Update n8n to 1.123.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5xrp-6693-jjx9 is resolved across your whole dependency graph.

How do I detect GHSA-5xrp-6693-jjx9 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n. 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-5xrp-6693-jjx9 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-5xrp-6693-jjx9?

O3 pinpoints whether GHSA-5xrp-6693-jjx9 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-5xrp-6693-jjx9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5xrp-6693-jjx9 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-5xrp-6693-jjx9?

GHSA-5xrp-6693-jjx9 has an EPSS (Exploit Prediction Scoring System) score of 18.7%, placing it in the 97th 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 warrants monitoring and prompt remediation.

When was GHSA-5xrp-6693-jjx9 published, and has it been updated?

GHSA-5xrp-6693-jjx9 was published on January 27, 2026 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-5xrp-6693-jjx9: n8n Remote Code Execution (Critical 9.9)

EPSS Exploitation Probability

via FIRST.org ↗

18.7%probability of exploitation in next 30 days

Moderate Risk97th percentile+16.47%

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

3 pkgs affected

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

n8nnpm

81Kdownloads / week

Description

n8n contains a critical Remote Code Execution (RCE) vulnerability in its workflow Expression evaluation system. Expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime.

An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`n8n`	all versions	1.123.17
📦npm	`n8n`	≥ 2.0.0&&< 2.4.5	2.4.5
📦npm	`n8n`	≥ 2.5.0&&< 2.5.1	2.5.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n. 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 to 1.123.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5xrp-6693-jjx9 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-5xrp-6693-jjx9 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-5xrp-6693-jjx9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

n8n contains a critical Remote Code Execution (RCE) vulnerability in its workflow Expression evaluation system. Expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operati

O3 Security · Impact-Aware SCA

Is GHSA-5xrp-6693-jjx9 in your dependencies?

O3 detects GHSA-5xrp-6693-jjx9 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-5xrp-6693-jjx9