---
id: CVE-2026-54310
title: 'n8n: SQL Injection in Postgres v1/TimesclaeDB Nodes'
summary: 'n8n: SQL Injection in Postgres v1/TimesclaeDB Nodes'
severity: medium
cvss: 9.9
cwe:
  - CWE-89
vendor: n8n
product: n8n
ecosystem: npm
affected:
  - 'n8n >= 2.26.0, < 2.26.2'
  - n8n < 2.25.7
patched:
  - n8n 2.26.2
  - n8n 2.25.7
published: '2026-06-16'
updated: '2026-06-16'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-c37g-w77q-m4vp'
references:
  - url: 'https://github.com/n8n-io/n8n/security/advisories/GHSA-c37g-w77q-m4vp'
  - url: 'https://github.com/advisories/GHSA-c37g-w77q-m4vp'
tags:
  - ghsa
  - npm
epss: 0.00545
epssPercentile: 0.43324
ingestedAt: '2026-06-29T14:31:47.727Z'
---

## Overview

## Impact
An authenticated user with permission to create or modify workflows could supply a crafted parameters to the TimescaleDB and/or legacy Postgres v1 node's allowing arbitrary SQL to be injected and executed against the connected database within the privileges of the configured database account.

## Patches
The issue has been fixed in n8n versions 2.25.7, and 2.26.2. 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:
- Limit workflow creation and editing permissions to fully trusted users only.
- Disable the Postgres and TimescaleDB node by adding `n8n-nodes-base.postgres`,  `n8n-nodes-base.timescaleDb` to the `NODES_EXCLUDE` environment variable.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

## Affected packages

- `n8n >= 2.26.0, < 2.26.2`
- `n8n < 2.25.7`

## Remediation

Upgrade to a patched release:

- `n8n 2.26.2`
- `n8n 2.25.7`