Skip to main content
CVE-2026-118643VulnerabilityPublished

n8n before 1.123.85, 2.x before 2.43.5, and 2.44.x before 2.44.1 stores credential secrets in execution error data

Affects n8nSource GCVE Database

0
Authoritative record:CVE-2026-118643· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium · fixed in 2.44.1 : update n8n when convenient.

Data as of 28 Oct 2026, 22:26 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.44.1, 2.43.5, 1.123.85
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade n8n to 2.44.1, 2.43.5 or 1.123.85.

Affected software

ProductAffectedFixed in
npmn8npkg:npm/n8nOther threatsAffected
  • <1.123.85
  • >=2.0.0 <2.43.5
  • >=2.44.0 <2.44.1
Fixed in
  • 1.123.85
  • 2.43.5
  • 2.44.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in n8n versions 1.123.85, 2.43.5, and 2.44.1. Users should upgrade to these or later versions to prevent credential secrets from being stored in execution error data. No vendor advisory content was provided to indicate alternative mitigations or that no action is required.

Description

n8n versions before 1.123.85, 2.x before 2.43.5, and 2.44.x before 2.44.1 improperly store credential secrets in execution error data for certain nodes. This exposure occurs when operations fail in the Git, MongoDB Atlas Vector Store, and Google Cloud Storage nodes. Users with permission to view workflow executions but without credential read access can extract sensitive secrets such as Git passwords or tokens, MongoDB passwords, and Google access tokens from the error data.

References

Community reviews

Loading reviews…