GHSA-2XCX-75H9-VR9H

Vulnerability from github – Published: 2026-02-04 20:33 – Updated: 2026-02-06 21:43
VLAI?
Summary
n8n's domain allowlist bypass enables credential exfiltration
Details

Impact

A vulnerability in the HTTP Request node's credential domain validation allowed an authenticated attacker to send requests with credentials to unintended domains, potentially leading to credential exfiltration.

This only might affect user who have credentials that use wildcard domain patterns (e.g., *.example.com) in the "Allowed domains" setting.

Patches

This issue is fixed in version 1.121.0 and later. All users are strongly encouraged to upgrade.

Workarounds

Until projects can upgrade:

  • Replace wildcard domain patterns with explicit domain listings in HTTP Request credentials
  • Review and restrict workflow creation/modification permissions to trusted users only
  • Audit existing workflows using HTTP Request nodes with domain-restricted credentials

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

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "n8n"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.121.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-25631"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-20"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-02-04T20:33:27Z",
    "nvd_published_at": "2026-02-06T21:16:18Z",
    "severity": "MODERATE"
  },
  "details": "## Impact\n\nA vulnerability in the HTTP Request node\u0027s credential domain validation allowed an authenticated attacker to send requests with credentials to unintended domains, potentially leading to credential exfiltration.\n\nThis only might affect user who have credentials that use wildcard domain patterns (e.g., `*.example.com`) in the \"Allowed domains\" setting.\n\n## Patches\n\nThis issue is fixed in version 1.121.0 and later. All users are strongly encouraged to upgrade.\n\n## Workarounds\nUntil projects can upgrade:\n\n- Replace wildcard domain patterns with explicit domain listings in HTTP Request credentials\n- Review and restrict workflow creation/modification permissions to trusted users only\n- Audit existing workflows using HTTP Request nodes with domain-restricted credentials\n\n---\nn8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backward compatibility.\n\nCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
  "id": "GHSA-2xcx-75h9-vr9h",
  "modified": "2026-02-06T21:43:45Z",
  "published": "2026-02-04T20:33:27Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/n8n-io/n8n/security/advisories/GHSA-2xcx-75h9-vr9h"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25631"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/n8n-io/n8n"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "n8n\u0027s domain allowlist bypass enables credential exfiltration"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…