CVE-2026-130715

NocoDB before 2026.08.0 SQL Injection via Zero-Argument Functions in Column Defaults

Published Nov 18, 2026 CVSS 4.0 · 7.1 High EPSS n/a KEV · Not listed
Description
NocoDB before 2026.08.0 contains an sql injection vulnerability that allows authenticated Creator or Owner users to execute database functions by supplying zero-argument function calls as column default values. Attackers can plant functions like version() or inet_server_addr() in PostgreSQL or MySQL column definitions and read results through record APIs, disclosing server addresses, role names, and engine details.

Analysis

AI-generated

Technical impact

NocoDB versions prior to 2026.08.0 suffer from a SQL injection flaw that enables an authenticated user with Creator or Owner privileges to inject zero‑argument database functions into column default definitions. By submitting function calls such as version() or inet_server_addr() when defining a column, the attacker can execute those functions against the underlying database. The result of the function is returned via the record API, allowing the attacker to read server information, role names and engine details, effectively disclosing internal configuration data.

Affected Systems

The affected product is NocoDB from the vendor nocodb, specifically all releases before 2026.08.0. The flaw exists in NocoDB's handling of column default values when connected to PostgreSQL or MySQL databases.

Risk and Exploitability

The vulnerability has a CVSS score of 7.1, indicating a high likelihood of moderate risk. Its EPSS is not available, and it is not listed in CISA's KEV catalog. Exploitation requires that the attacker already possesses Creator or Owner credentials within the NocoDB instance, which provides sufficient access to create or modify column definitions. Once those privileges are in place, the attack is straightforward: inject the desired zero‑argument function into a column default, commit the change, and retrieve the function’s output through existing record retrieval endpoints. Because the flaw can surface internal database metadata, the impact is primarily information disclosure within a trusted environment rather than remote code execution.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update to NocoDB 2026.08.0 or a later released version to remove the injection vector.
  • If an upgrade cannot be performed immediately, audit and delete any column defaults that contain zero‑argument functions, and consider disabling the permission for Creator or Owner users to modify column definitions until a patch is applied.
  • Restrict the database user that NocoDB uses by limiting its privileges to only those required for normal operation, preventing execution of arbitrary database functions.

Generated by OpenCVE AI on November 18, 2026 at 19:12 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description NocoDB before 2026.08.0 contains an sql injection vulnerability that allows authenticated Creator or Owner users to execute database functions by supplying zero-argument function calls as column default values. Attackers can plant functions like version() or inet_server_addr() in PostgreSQL or MySQL column definitions and read results through record APIs, disclosing server addresses, role names, and engine details.
Title NocoDB before 2026.08.0 SQL Injection via Zero-Argument Functions in Column Defaults
First Time appeared Nocodb
Nocodb nocodb
Weaknesses CWE-89
CPEs cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*
Vendors & Products Nocodb
Nocodb nocodb
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 18, 2026, 5:53 PM
Reserved
Nov 17, 2026, 3:38 PM
Status
Received
Published
Nov 18, 2026, 12:17 PM
Modified
Nov 18, 2026, 6:19 PM