Skip to content
Applications

CVE-2026-33713

8.7
High
EPSS 0.42%Patch availableMar 26, 2026

Authenticated SQL injection in n8n Data Table Get node.

triage
server-sideruntimeWAF · effectiveAV · networkCWE-89· SQL Injection

WAF coverage: SQL injection. Signatures match well at the request layer.

Also consider: parameterized queries · ORM

cvss vector
attack vectornetworkattack complexitylowprivileges requiredlowuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2026-33713 being exploited?

Not confirmed. CVE-2026-33713 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.42% probability of exploitation in the next 30 days.

How severe is CVE-2026-33713?

CVE-2026-33713 is rated High with a CVSS score of 8.7. 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-33713?

Yes. A fix has been recorded for CVE-2026-33713. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-33713 affect?

CVE-2026-33713 affects n8n workflow automation platform. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-33713?

Upgrade to fixed versions (1.123.26+, 2.13.3+, 2.14.1+); audit Data Table Get nodes.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
n8n workflow automation platform
impact

Auth user can modify/delete data via SQL injection; PostgreSQL supports multi-statement execution.

action required

Patch when possible

affected versions
n8n-io n8n
  • affected< 1.123.26
  • affected>= 2.0.0-rc.0 and < 2.13.3
  • affected= 2.14.0

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free