External risk intelligence

NocoDB Authorization Bypass Allows Tenant Data Access

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-130712

NocoDB is a web-based database management platform commonly deployed as an internet-facing application, API, or service to provide remote database access and administration, placing this functionality squarely in the path of network-reachable web traffic.

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

NocoDB, a web-based database management platform, has a vulnerability that allows authenticated users to bypass authorization controls and access sensitive data from other tenants. This could lead to unauthorized viewing, modification, or insertion of records within databases.

  • Authenticated users can access other tenants' data.
  • Protects sensitive, shared database information.
  • Confirm NocoDB relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker with creator privileges can exploit this vulnerability by reusing a victim's source ID when adding their own external database source. This bypasses authorization controls and allows the attacker to access and manipulate the victim's tenant database through their own base models, potentially leading to data breaches and unauthorized modifications.

  • Authenticated creator access required.
  • Reusing victim source ID bypasses authorization.
  • Unauthorized access to tenant database.

Live Threat

Current exploitation, exposure, and threat context

Authenticated users could access and manipulate data within different tenants' external databases. This vulnerability may affect service integrity and tenant data confidentiality under supported configurations.

  • Tenant external database access.
  • Authenticated user reuses source ID.
  • Unauthorized data reading and modification.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in NocoDB likely impacts teams responsible for managing internal and external database access, such as application owners and platform teams, especially if NocoDB is exposed externally or used for multi-tenant data. The first practical step is to identify all NocoDB instances, determine their exposure, and ascertain which tenant data might be at risk.

  • Application owners must confirm NocoDB deployment.
  • Verify tenant data segregation and access controls.
  • Plan remediation based on exposure and business criticality.

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 and how is it used?

NocoDB is an open-source platform that turns any relational database into a smart spreadsheet interface. Teams use it to build collaborative tools, manage data records, and provide accessible database administration without requiring complex SQL knowledge. By acting as a bridge between raw database storage and user-friendly views, it simplifies how organizations manage and share their data across different business workflows.

What does CVE-2026-130712 mean for data security?

This vulnerability is an authorization bypass, specifically categorized as CWE-639: Authorization Bypass Through User-Controlled Key. It means the software fails to properly verify that a user has permission to access a specific data source. Because the system improperly trusts a supplied source ID, an attacker can trick the application into connecting to a database belonging to another tenant, effectively breaking the logical isolation between different users.

How does an attacker trigger this authorization bypass?

An attacker needs an existing authenticated account with 'Creator' privileges. The trigger occurs when the attacker adds a new external database source and provides a victim's source ID. The system's connection manager caches database connections based on this ID alone, causing it to incorrectly map the attacker's session to the victim's database. Simply having an account without these specific privileges or failing to supply a valid, existing source ID prevents this issue.

Is my NocoDB instance at risk?

According to Halo Surface Signal, NocoDB is frequently deployed as an internet-facing service to facilitate remote database administration, which places it directly in the path of network traffic. If your instance is accessible over the internet or supports multi-tenant environments where users share the same infrastructure, the potential for unauthorized cross-tenant data access is significantly higher.

How should I respond if I use NocoDB?

The immediate priority is to locate all NocoDB deployments within your environment and determine their current network exposure. Once identified, evaluate your user access controls, specifically focusing on which accounts hold 'Creator' privileges. Review your internal records to confirm if your deployment model involves multi-tenant data, then prioritize applying the necessary software updates to address the underlying authorization flaw.

References