GHSA-5VJ6-WJR7-5V9F

Vulnerability from github – Published: 2025-06-27 14:19 – Updated: 2025-06-27 14:19
VLAI?
Summary
n8n allows open redirects via the /signin endpoint
Details

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

Severity ?
4.6 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 1.97.0"
      },
      "package": {
        "ecosystem": "npm",
        "name": "n8n"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.98.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-49592"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-601"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-06-27T14:19:01Z",
    "nvd_published_at": "2025-06-26T20:15:29Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n\nThis 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.\n\nThis may lead to:\n\n- Phishing attacks by impersonating the n8n UI on lookalike domains (e.g., n8n.local.evil.com)\n- Credential or 2FA theft if users are tricked into re-entering sensitive information\n- Reputation risk due to the visual similarity between attacker-controlled domains and trusted ones\n\nThe vulnerability affects anyone hosting n8n and exposing the `/signin` endpoint to users.\n\n### Patches\n\nThe issue has been patched in [1.98.0](https://github.com/n8n-io/n8n/releases/tag/n8n%401.98.0).\nAll users should upgrade to this version or later.\n\nThe fix introduces strict origin validation for redirect URLs, ensuring only same-origin or relative paths are allowed after login.\n\nPatch commit: https://github.com/n8n-io/n8n/pull/16034",
  "id": "GHSA-5vj6-wjr7-5v9f",
  "modified": "2025-06-27T14:19:02Z",
  "published": "2025-06-27T14:19:01Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/n8n-io/n8n/security/advisories/GHSA-5vj6-wjr7-5v9f"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-49592"
    },
    {
      "type": "WEB",
      "url": "https://github.com/n8n-io/n8n/pull/16034"
    },
    {
      "type": "WEB",
      "url": "https://github.com/n8n-io/n8n/commit/4865d1e360a0fe7b045e295b5e1a29daad12314e"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/n8n-io/n8n"
    },
    {
      "type": "WEB",
      "url": "https://github.com/n8n-io/n8n/releases/tag/n8n%401.98.0"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "n8n allows open redirects via the /signin endpoint"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.