CVE-2026-71539
Authenticated user can plant malicious JS via Git node symlink, causing server RCE.
Is CVE-2026-71539 being exploited?
Not confirmed. CVE-2026-71539 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-71539?
CVE-2026-71539 is rated High with a CVSS score of 8.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-71539?
Yes. A fix has been recorded for CVE-2026-71539. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-71539 affect?
CVE-2026-71539 affects n8n < 1.123.64, n8n < 2.29.8, n8n < 2.30.1, n8n Git node, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71539?
Upgrade to 1.123.64, 2.29.8, or 2.30.1; restrict Git node access and audit community nodes.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated workflow user can achieve remote code execution by planting a crafted JS node in community directory loaded on restart.
Immediate action required
- affected< 1.123.64
- affected>= 2.0.0-rc.0 and < 2.29.8
- affected>= 2.30.0 and < 2.30.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.