CVE-2026-126285 in NocoDBinfo

Summary

by MITRE • 11/13/2026

NocoDB before 2026.08.0 contains an sql injection vulnerability that allows authenticated users with read access to run arbitrary read queries via the legacy where parameter on PostgreSQL. Attackers, including Viewer-role users, can inject single quotes into filter values concatenated by CustomKnex.ts to read other tables, schemas, view-filtered rows, and hidden columns.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/13/2026

NocoDB versions prior to 2026.08.0 contain a critical SQL injection vulnerability within the legacy where parameter handling mechanism for PostgreSQL databases. This flaw allows authenticated users with even minimal read access privileges to execute arbitrary read queries against the underlying database. The root cause lies in improper input sanitization and dynamic query construction within the CustomKnex.ts module, which concatenates user-supplied filter values directly into SQL statements without adequate escaping or parameterized query usage. Consequently, attackers can inject single quotes and other SQL metacharacters to manipulate the intended logic of the database queries.

The operational impact of this vulnerability is significant for organizations relying on NocoDB as a no-code platform for internal data management. Since the flaw affects authenticated users with read access, it effectively lowers the barrier for exploitation compared to unauthenticated attacks. An attacker possessing Viewer-role privileges can bypass intended data isolation boundaries by injecting SQL code that reads other tables, accesses different schemas, retrieves rows filtered out by view configurations, and extracts hidden columns that are not exposed through the standard user interface. This capability undermines the principle of least privilege and allows for comprehensive enumeration of the database structure and contents beyond what was originally permitted.

From a classification perspective, this vulnerability aligns with CWE-89 Improper Neutralization of Special Elements used in an SQL Command, commonly known as SQL Injection. The specific technique employed involves manipulating input parameters to alter query execution paths, which maps to ATT&CK tactic T1059 Command and Scripting Interpreter via database commands or more specifically the data exfiltration techniques associated with lateral movement through compromised credentials if combined with other exploits. However, in this context, it primarily facilitates unauthorized data access under T1530 Data from Cloud Storage Object or local equivalent depending on deployment model, leveraging valid authentication to extract sensitive information.

Mitigation strategies should prioritize immediate upgrading to NocoDB version 2026.08.0 or later where the issue has been resolved by implementing proper parameterized queries and input validation within the CustomKnex.ts module. For environments that cannot be immediately patched, administrators should enforce strict role-based access control policies, ensuring that users with read-only permissions are restricted from using advanced filtering features if possible. Additionally, deploying a Web Application Firewall can provide an additional layer of defense by detecting and blocking common SQL injection patterns in HTTP requests targeting the affected endpoints. Regular security audits and code reviews focusing on dynamic query construction practices will help prevent similar vulnerabilities in future development cycles.

Responsible

VulnCheck

Reservation

11/10/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00289

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!