Is n8n affected by CVE-2026-42231?

npm n8n is affected in =2.18.0 =2.17.0 <2.17.4.

Is CVE-2026-42231 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.9%.

critical

CVE-2026-42231

Q: Is CVE-2026-42231 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.9%.

npm · n8n

Summary

n8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCE

Severity: critical
EPSS: 0.9% (p53)
Also known as: GHSA-q5f4-99jv-pgg5
Published: 2026-04-29

References

https://github.com/n8n-io/n8n/security/advisories/GHSA-q5f4-99jv-pgg5
https://nvd.nist.gov/vuln/detail/CVE-2026-42231
https://github.com/n8n-io/n8n

Related advisories

CVE-2026-44791 — critical · npm/n8n
CVE-2026-44790 — critical · npm/n8n
CVE-2026-44789 — critical · npm/n8n
CVE-2026-42232 — critical · npm/n8n
CVE-2025-68613 — critical · npm/n8n
CVE-2026-54304 — high · npm/n8n
CVE-2026-54309 — high · npm/n8n
CVE-2026-54305 — high · npm/n8n

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.