External risk intelligence

NocoDB OAuth Token Authentication Bypass Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-130730

NocoDB is a web-based database management platform designed to be accessed via web browsers and APIs. These applications are commonly deployed as internet-facing services to allow remote collaboration and data management, making them likely to be reachable from the public internet in standard deployment scenarios.

Authentication Bypass

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 advisory concerns a vulnerability in NocoDB that allows unauthorized access. An attacker could exploit this by manipulating authentication tokens, potentially granting them the same privileges as a legitimate user. The primary concern is to confirm if NocoDB is in use and if it is exposed to potential threats.

  • Authentication bypass in NocoDB.
  • Allows unauthorized access via manipulated tokens.
  • Confirm NocoDB usage and exposure.

Attack Path

How an attacker could exploit the issue

An attacker could leverage an OAuth token to bypass authentication and gain unauthorized access to a NocoDB instance. By presenting a valid, but narrowly scoped, OAuth token during specific interactions like session establishment or API handshakes, the attacker can impersonate the legitimate user associated with that token, effectively achieving full session privileges without proper authentication. This vulnerability could lead to sensitive data exposure and unauthorized modifications.

  • Requires a valid OAuth token.
  • Bypasses authentication via token exchange.
  • Grants full user privileges.

Live Threat

Current exploitation, exposure, and threat context

NocoDB instances that allow OAuth authentication could be vulnerable to an authentication bypass. When supported, an attacker with a narrowly scoped OAuth token could present it to bypass session management, potentially gaining the privileges of the user who granted the token.

  • User session data
  • OAuth token validation
  • Unauthorized data access

Operational Fix

Recommended remediation, mitigation, and detection steps

The description indicates NocoDB is a web-based application, suggesting that teams responsible for application hosting and security, such as infrastructure, platform, or security operations, should lead the response. The initial practical step involves identifying all NocoDB instances, confirming their exposure and business criticality, and locating the accountable owner before planning any remediation.

  • Identify and assess NocoDB instances.
  • Confirm reachability and business criticality.
  • Plan remediation with the accountable owner.

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 spreadsheet interface. It provides a visual layer for managing database records, creating APIs, and enabling collaborative data workflows. Because it functions as a web-based database management tool, it is frequently hosted on servers to allow teams to access and manipulate data remotely through browsers or API connections.

What does CWE-287 mean for CVE-2026-130730?

CWE-287 refers to Improper Authentication. In the context of this vulnerability, the system fails to correctly verify the scope or authority of an OAuth token. Instead of enforcing the intended restrictions of that token, NocoDB mistakenly treats it as a credential for a full, privileged user session. Essentially, the software is tricked into granting administrative-level access based on a token that should have had very limited permissions.

How can an attacker trigger this vulnerability?

An attacker needs access to a legitimately issued, narrowly scoped OAuth token. They then present this token to specific NocoDB endpoints, such as the session strategy, token exchange, or NocoSocket handshake processes. It is important to note that simply having access to the NocoDB interface does not trigger the bug; the attacker must possess a valid OAuth token to initiate the fraudulent session upgrade.

Is my NocoDB instance at risk?

According to Halo Surface Signal, NocoDB instances are often deployed as internet-facing services to facilitate remote data management, which increases the likelihood of external reachability. If your instance is accessible from the public internet and has OAuth authentication enabled, it is in a configuration where this bypass could be attempted by anyone holding a valid but restricted token.

What should I do if I run NocoDB?

Begin by auditing your environment to locate all active NocoDB instances and confirm if they utilize OAuth for authentication. Determine which instances are reachable over the network and verify their business criticality with the system owners. Prioritize these deployments for review and prepare to implement the vendor's updates or security guidance to ensure authentication mechanisms are properly enforced.

References