CVE-2026-42227 — HIGH (CVSS 7.7) AI Security Vulnerability

Q: What is CVE-2026-42227?

n8n has Public API Variables IDOR that Allows Cross-Project Secret Disclosure

Q: Is CVE-2026-42227 actively exploited?

No confirmed active exploitation of CVE-2026-42227 has been reported, but organizations should still patch proactively.

Q: How to fix CVE-2026-42227?

Update to patched version: n8n 1.123.32.

Q: What is the CVSS score for CVE-2026-42227?

CVE-2026-42227 has a CVSS v3.1 base score of 7.7 (HIGH).

## Impact An authenticated user with a valid API key scoped to `variable:list` could read variables from projects they are not a member of by supplying an arbitrary `projectId` query parameter to the public API variables endpoint. The handler queried the variables repository directly without...

Full CISO analysis pending enrichment.

Affected Systems

Package	Ecosystem	Vulnerable Range	Patched
n8n	npm	< 1.123.32	`1.123.32`
185.6K OpenSSF 6.0 16 dependents Pushed 4d ago 38% patched ~1d to patch Full package profile →

Do you use n8n? You're affected.

Severity & Risk

CVSS 3.1

7.7 / 10

EPSS

N/A

Exploitation Status

No known exploitation

Sophistication

N/A

Attack Surface

AV Network

AC Low

PR Low

UI None

S Changed

C High

I None

A None

Recommended Action

Patch available

Update n8n to version 1.123.32

Compliance Impact

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is CVE-2026-42227?

n8n has Public API Variables IDOR that Allows Cross-Project Secret Disclosure

Is CVE-2026-42227 actively exploited?

No confirmed active exploitation of CVE-2026-42227 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-42227?

Update to patched version: n8n 1.123.32.

What is the CVSS score for CVE-2026-42227?

CVE-2026-42227 has a CVSS v3.1 base score of 7.7 (HIGH).

Technical Details

NVD Description

## Impact An authenticated user with a valid API key scoped to `variable:list` could read variables from projects they are not a member of by supplying an arbitrary `projectId` query parameter to the public API variables endpoint. The handler queried the variables repository directly without enforcing project membership checks, bypassing the authorization-aware service layer used by the internal enterprise controller. If variables were misused to store sensitive information such as credentials or tokens, they should be rotated immediately. This issue only affects licensed enterprise or team deployments with multiple projects and the variables feature enabled. ## Patches The issue has been fixed in n8n versions 1.123.32, 2.17.4, and 2.18.1. Users should upgrade to one of these versions or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict n8n access and API key issuance to fully trusted users only. - Audit existing project variables for sensitive values and rotate any secrets that may have been exposed. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.