Quick answers
- Is CVE-2026-118643 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118643 being exploited in the wild.
- How severe is CVE-2026-118643?
- High severity, with a CVSS score of 8.2, published 28 October 2026.
- Which products and versions are affected?
- N8n before 1.123.85, 2.0.0 before 2.43.5, 2.44.0 before 2.44.1.
- Is there a fix for CVE-2026-118643?
- Yes: fixed in n8n 1.123.85, 2.43.5, 2.44.1. Until then: Restrict n8n instance access to fully trusted users only and limit execution read access to the minimum set of users who require it until upgrading. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118643 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-118643?
- Check whether you run N8n at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: n8n 1.123.85, 2.43.5, 2.44.1
Restrict n8n instance access to fully trusted users only and limit execution read access to the minimum set of users who require it until upgrading.
Technical details
A CWE-209 sensitive information disclosure vulnerability in the Git, MongoDB Atlas Vector Store, and Google Cloud Storage nodes stores credential secrets in unencrypted execution error data when operations fail. An attacker with workflow execution read access but insufficient credential permissions can extract Git passwords/tokens, MongoDB database passwords, or Google access tokens from error logs. The vulnerability requires low privileges and network access with no user interaction.
Affected products
- n8n n8n before 1.123.85, 2.0.0 before 2.43.5, 2.44.0 before 2.44.1
Timeline
- 2026-10-14: disclosed
- 2026-10-28: advisory