External risk intelligence

NocoDB SQL Injection via Crafted Formula Persistence

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-130706

NocoDB is a web-based database management platform commonly deployed as a public-facing web application or API service. While the vulnerability requires authenticated access as a Creator or Owner, the application itself is typically exposed to the internet in normal enterprise or personal deployments to facilitate remote database management and collaboration.

SQL Injection

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability in NocoDB, a web-based database management platform, allows authenticated users with Creator or Owner roles to inject malicious SQL commands. Exploitation could lead to escalating privileges to super administrator or executing operating system commands on connected PostgreSQL hosts, potentially impacting data confidentiality, integrity, and availability.

  • SQL injection in NocoDB.
  • Potential for high-impact unauthorized access.
  • Confirm relevance and potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker with Creator or Owner privileges can exploit this vulnerability by crafting a specific formula that bypasses security checks. This allows them to inject malicious SQL code, potentially leading to elevated privileges or the execution of commands on external systems.

  • Requires authenticated Creator/Owner access.
  • Crafted formula injected via parsed tree.
  • Risk of privilege escalation or command execution.

Live Threat

Current exploitation, exposure, and threat context

Authenticated Creator or Owner users could inject raw SQL by reusing a crafted formula without revalidation, potentially bypassing security measures to gain super administrator privileges or execute OS commands on external PostgreSQL hosts.

  • System data and service behavior.
  • Authenticated user with crafted input.
  • Unauthorized access or command execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

NocoDB application owners and platform teams are likely responsible for addressing this vulnerability, as it affects the core functionality of the database management platform. The first practical step is to identify all NocoDB instances, confirm their external reachability and business criticality, and then determine the specific accountable owner for each instance to plan remediation.

  • Application and platform teams own this.
  • Verify external reachability and criticality.
  • Plan remediation with vendor and owners.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is NocoDB?

NocoDB is an open-source platform that turns any relational database into a smart, collaborative spreadsheet interface. Teams use it to build database-backed applications and manage data records without writing complex code. Because it acts as a central hub for database management, it is frequently installed as a web-accessible service to allow remote collaboration across distributed teams.

How does CVE-2026-130706 work?

This vulnerability is an SQL Injection, classified as CWE-89. It occurs because NocoDB fails to properly revalidate formula data that has been saved and reused. An authenticated user can supply a maliciously crafted formula that the system treats as trusted input, allowing them to inject raw SQL commands directly into the underlying database engine.

Do I need to worry if I am not a NocoDB administrator?

The bug specifically requires authenticated access as a user with Creator or Owner privileges to trigger the flaw. Standard viewers or users without these elevated permissions cannot initiate the malicious formula persistence. Furthermore, simple database operations that do not involve saving or reusing formula structures do not trigger this vulnerability.

Is my NocoDB instance at risk?

According to Halo Surface Signal, NocoDB is frequently deployed as a public-facing web application or API. If your instance is accessible via the internet, it is considered higher risk because remote attackers—who may have gained unauthorized Creator or Owner accounts—can reach the application without needing local network access to execute commands or escalate privileges.

How should I respond to this NocoDB issue?

Start by auditing your environment to locate every running NocoDB instance. Determine which systems are reachable from the public internet versus those restricted to internal networks. Once identified, assign clear ownership for each deployment so that technical teams can coordinate the necessary updates to secure the application against this injection flaw.

References