How severe is GHSA-5vj6-wjr7-5v9f?

GHSA-5vj6-wjr7-5v9f has a CVSS score of 4.6/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-5vj6-wjr7-5v9f?

GHSA-5vj6-wjr7-5v9f affects the following packages: n8n (npm). Ecosystems affected: npm.

How do I fix GHSA-5vj6-wjr7-5v9f?

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

How do I detect GHSA-5vj6-wjr7-5v9f 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-5vj6-wjr7-5v9f 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-5vj6-wjr7-5v9f?

O3 pinpoints whether GHSA-5vj6-wjr7-5v9f 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-5vj6-wjr7-5v9f actively exploited in the wild?

No public exploit code has been indexed for GHSA-5vj6-wjr7-5v9f 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-5vj6-wjr7-5v9f?

GHSA-5vj6-wjr7-5v9f has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 9th 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-5vj6-wjr7-5v9f?

GHSA-5vj6-wjr7-5v9f is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-5vj6-wjr7-5v9f published, and has it been updated?

GHSA-5vj6-wjr7-5v9f was published on June 27, 2025 and was last updated on June 27, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-5vj6-wjr7-5v9f

MEDIUM

n8n allows open redirects via the /signin endpoint

Also known asCVE-2025-49592

Published

Jun 27, 2025

Updated

Jun 27, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk9th percentile+0.01%

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.

n8nnpm

85Kdownloads / week

Description

Impact

This is an Open Redirect (CWE-601) vulnerability in the login flow of n8n. Authenticated users can be redirected to untrusted, attacker-controlled domains after logging in, by crafting malicious URLs with a misleading redirect query parameter.

This may lead to:

Phishing attacks by impersonating the n8n UI on lookalike domains (e.g., n8n.local.evil.com)
Credential or 2FA theft if users are tricked into re-entering sensitive information
Reputation risk due to the visual similarity between attacker-controlled domains and trusted ones

The vulnerability affects anyone hosting n8n and exposing the /signin endpoint to users.

Patches

The issue has been patched in 1.98.0. All users should upgrade to this version or later.

The fix introduces strict origin validation for redirect URLs, ensuring only same-origin or relative paths are allowed after login.

Patch commit: https://github.com/n8n-io/n8n/pull/16034

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`n8n`	all versions	1.98.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. 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.98.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5vj6-wjr7-5v9f 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-5vj6-wjr7-5v9f 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-5vj6-wjr7-5v9f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact This is an Open Redirect (CWE-601) vulnerability in the login flow of n8n. Authenticated users can be redirected to untrusted, attacker-controlled domains after logging in, by crafting malicious URLs with a misleading redirect query parameter. This may lead to: - Phishing attacks by impersonating the n8n UI on lookalike domains (e.g., n8n.local.evil.com) - Credential or 2FA theft if users are tricked into re-entering sensitive information - Reputation risk due to the visual similarity between attacker-controlled domains and trusted ones The vulnerability affects anyone hosting n

O3 Security · Impact-Aware SCA

Is GHSA-5vj6-wjr7-5v9f in your dependencies?

O3 detects GHSA-5vj6-wjr7-5v9f 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