Quick answers
- Is CVE-2026-118676 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118676 being exploited in the wild.
- How severe is CVE-2026-118676?
- High severity, with a CVSS score of 7.1, published 28 October 2026.
- Which products and versions are affected?
- N8n before 1.123.85, 2.43.5, and 2.44.1.
- Is there a fix for CVE-2026-118676?
- Yes: fixed in 1.123.85, 2.43.5, 2.44.1. Until then: Restrict n8n instance access to fully trusted users only. Audit credential ownership and remove credentials that should not be accessible to member-level users. Monitor execution logs for unexpected credential usage by member accounts. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118676 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-118676?
- 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: 1.123.85, 2.43.5, 2.44.1
Restrict n8n instance access to fully trusted users only. Audit credential ownership and remove credentials that should not be accessible to member-level users. Monitor execution logs for unexpected credential usage by member accounts.
Technical details
The vulnerability exists in n8n's pre-execution credential permission validation. The check only examines credential slots considered "active" based on stored parameters, where default values are omitted. At execution time, defaults are restored and the node uses the credential, bypassing the authorization check. A member user can save and execute workflows referencing credentials they lack access to, causing decrypted credential values to be exfiltrated.
Affected products
- n8n n8n before 1.123.85, 2.43.5, and 2.44.1
Timeline
- 2026-10-14: disclosed
- 2026-10-28: advisory