CVE-2025-49592 is a medium-severity (CVSS 4.6) Open Redirect vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.
n8n Login Flow has Open Redirect Vulnerability
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 CVE-2025-49592.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
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.
n8nnpmDescription
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | n8n | all versions | 1.98.0npm install n8n@1.98.0 |
Affected Products
n8nn8nDetection & mitigation playbook
Open-source dependencyDetect
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.98.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-49592 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.
Frequently Asked Questions
Is CVE-2025-49592 in your dependencies?
Find it across npm, including transitive dependencies.