Cyber Resilience

CVE-2026-59206

N8N ≤ 1.123.61

Published
09 July 2026
Modified
09 July 2026
Patch / advisory
CVSS Score v4 7.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0030 22th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-59206 is a high-severity Prototype Pollution (CWE-1321) vulnerability in N8N N8N. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-6 (Least Privilege) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

n8n is an open source workflow automation platform. Prior to 1.123.61, 2.27.4, and, 2.28.1, an authenticated user with the default workflow:create permission could pollute Object.prototype through a crafted workflow saved, updated, or imported via the workflow API, allowing unauthenticated requests…

more

to be treated as a privileged user and exposing user and project listing endpoints. This issue is fixed in versions 1.123.61, 2.27.4, and 2.28.1.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
Why these techniques?

Prototype pollution via the workflow API (CWE-1321) allows an authenticated user to escalate privileges, enabling exploitation of public-facing workflow endpoints (T1190) and abuse of elevation control mechanisms to gain higher privileges (T1068).

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-42231Same product: N8N N8N
CVE-2026-44791Same product: N8N N8N
CVE-2026-44789Same product: N8N N8N
CVE-2026-54306Same product: N8N N8N
CVE-2026-33696Same product: N8N N8N
CVE-2026-42232Same product: N8N N8N
CVE-2026-65595Same product: N8N N8N
CVE-2026-54312Same product: N8N N8N
CVE-2026-25056Same product: N8N N8N
CVE-2026-33665Same product: N8N N8N

Affected Assets

n8n
n8n
2.28.0 · ≤ 1.123.61 · 2.0.0 — 2.27.4

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • AC-6 Least Privilege
Detect
Catch it (NIST detect / respond)
  • SI-7 Software, Firmware, and Information Integrity
Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V15.3.6

Mitigating Controls (NIST 800-53 r5) AI

prevent

Enforces strict validation of workflow JSON input to block prototype-pollution payloads before they are saved or imported.

prevent

Restricts the workflow:create permission to only those roles that legitimately require it, reducing the attack surface for authenticated prototype-pollution abuse.

detect

Verifies the integrity of workflow objects on load/import, enabling detection of unauthorized prototype modifications that could elevate privileges.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and safe property assignment to prevent prototype pollution.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing in development catches prototype-pollution flaws before release.

prevents

Secure development lifecycle mandates input validation and object-handling controls that directly prevent prototype pollution.

prevents

Application security requirements explicitly call for safeguards against unsafe object attribute manipulation.

prevents

Secure architecture principles reduce the likelihood of prototype pollution through safe design patterns.

prevents

Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.

prevents

Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.

References