CVE-2026-47375: NocoDB: Postgres SQL Injection in Formula `ARRAYSORT`
Summary An authenticated user with columnAdd permission on a Postgres-backed base can inject arbitrary SQL into the formula engine via the optional direction argument of ARRAYSORT(...). The value is unrestricted by formula validation and embedded into a knex.raw ORDER BY clause, executing during column creation and on every subsequent record read of the formula column.
Published Jun 5, 2026 · Updated Jul 20, 2026
Affected packages
nocodb
- Ecosystem
- npm
- Affected
- < 2026.04.1
- Fixed in
- 2026.04.1
- Check
npm ls nocodb
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
An authenticated user with columnAdd permission on a Postgres-backed base can inject arbitrary SQL into the formula engine via the optional direction argument of ARRAYSORT(...). The value is unrestricted by formula validation and embedded into a knex.raw ORDER BY clause, executing during column creation and on every subsequent record read of the formula column.
Details
The vulnerability is specific to the Postgres mapping for ARRAYSORT in packages/nocodb/src/db/functionMappings/pg.ts. Two factors combine:
ARRAYSORTdeclares only argument count, notvalidation.args.type, sovalidate-extract-tree.tsdoes not enforce an allowlist on the second argument.- The Postgres mapping then passes the attacker-controlled value through
sanitize(knex.raw(...))into a raw SQL fragment:
const direction = pt.arguments[1]
? sanitize(
knex.raw(pt.arguments[1]?.value ?? (await fn(pt.arguments[1])).builder),
)
: knex.raw('asc');
return {
builder: knex.raw(`ARRAY(SELECT UNNEST(??) ORDER BY 1 ??)`, [source, direction]),
};sanitize() in sqlSanitize.ts only escapes ? placeholder characters; it does not validate SQL syntax. A payload such as "desc, (SELECT COUNT(*) FROM generate_series(1,30000000))" is accepted, persisted, and re-executed on every read of the formula column.
Impact
- Authenticated SQL injection against Postgres-backed bases.
- Requires
columnAddpermission (creator/owner-level). - Proven impact: attacker-controlled heavy SQL causing multi-second query stalls (DoS).
- Potentially extendable to broader SQL injection outcomes depending on database permissions and deployment hardening.
- Limited to Postgres backends.
Credit
This issue was reported by @leduckhuong.
Credited to leduckhuong.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-53927
NocoDB: Server-Side Request Forgery via Spreadsheet Fetch URL
medium5.1No fixJun 17, 2026CVE-2026-53928
NocoDB: Refresh Tokens Persist Through Password Recovery
medium6.3No fixJun 17, 2026CVE-2026-53929
NocoDB: Stored Cross-Site Scripting via Secure Attachment
medium5.1No fixJun 17, 2026CVE-2026-53930
NocoDB: Server-Side Request Forgery via Base Migration URL
medium5.1No fixJun 17, 2026CVE-2026-53931
NocoDB: Server-Side Request Forgery via Spreadsheet Import Endpoint
medium6.9No fixJun 17, 2026CVE-2026-47279
NocoDB: Hidden LTAR Column Exposure in Public Shared-View Relation Endpoints
medium6.9Jun 5, 2026
