NocoDB versions prior to 2026.09.0 have a missing authorization vulnerability in the job status polling endpoint. This flaw allows unauthenticated attackers who know a job ID to access buffered status messages and completion payloads. Sensitive information such as signed export download URLs or new base identifiers may be exposed. The vulnerability is fixed in version 2026.09.0.
NocoDB versions before 2026.09.0 have a server-side template injection vulnerability that allows authenticated users with Creator or Owner roles to execute arbitrary JavaScript. This occurs through abuse of Handlebars webhook helpers, enabling attackers to reach the Function constructor and execute operating system commands.
NocoDB before 2026.09.0 contains an improper authorization vulnerability that allows workspace Creator users to read plaintext notification webhook URLs by querying the webhook plugin listing endpoint. Attackers can replay exposed Slack, Teams, Discord and Mattermost webhook URLs directly against messaging providers to post arbitrary messages into organization chat channels.
NocoDB versions prior to 2026.09.0 contain a critical SQL injection vulnerability. Authenticated users with Creator or Owner roles can inject raw SQL through a crafted formula that bypasses SQLite metadata protections. This flaw allows escalation to super administrator privileges or execution of OS commands on external PostgreSQL hosts. The vulnerability is fixed in version 2026.09.0.
NocoDB versions from 0.301.4 up to but not including 2026.10.1 have a vulnerability where the nc_token session cookie is set without the Secure attribute in HTTPS sessions. This allows network attackers to potentially capture the session token by observing or inducing plain HTTP requests to HTTPS instances, enabling session impersonation until the token expires. The issue is fixed in version 2026.10.1.
NocoDB versions prior to 2026.10.0 have an improper access control vulnerability that allows users with Creator roles to exploit internal database attachment functionality. By supplying specific flags (is_meta and is_local), attackers can expose sensitive tables containing user, token, and integration data, enabling them to read and modify records including user roles.
NocoDB versions before 2026.10.1 have an information disclosure vulnerability that allows unauthenticated users holding shared view links to access hidden columns. By exploiting the public group-by endpoint with specific parameters, attackers can reveal hidden column values, counts, and existence. This vulnerability is fixed in version 2026.10.1.
NocoDB versions before 2026.10.0 contain an account takeover vulnerability. Users with the base creator role can exploit the baseUserInviteResend function to generate a new invite token, read it from the base member list, and reset the victim's password via signup. This allows attackers to hijack accounts, including owner or super admin accounts.
NocoDB versions prior to 2026.10.0 have an information disclosure vulnerability that allows unauthenticated attackers to access hidden column data. This occurs when attackers supply comma-separated group-by column lists, enabling them to bypass restrictions on shared view links and retrieve hidden values tied to individual rows.
NocoDB versions before 2026.10.1 have an SQL injection vulnerability due to improper escaping of backslashes in select-field option titles embedded in MySQL or MariaDB enum/set column definitions. This flaw allows a base creator or owner to manipulate option titles to inject malicious ALTER TABLE commands, potentially modifying database schema elements such as columns and indexes.
NocoDB versions before 2026.10.1 contain a consent phishing vulnerability via an unauthenticated dynamic OAuth client registration endpoint. This flaw allows attackers to register OAuth clients with arbitrary HTTPS redirect URIs and impersonate trusted applications on consent screens that lack proper warnings. Successful exploitation can lead to attackers obtaining tokens with read and write access to victim tables and records.
NocoDB versions from 0.301.4 up to but not including 2026.10.0 contain an information disclosure vulnerability. Authenticated workspace viewers can access pending invitation tokens via the workspace member list. These tokens can be redeemed by attackers to claim invited accounts and escalate privileges to roles such as workspace owner. The vulnerability is rated high severity with a CVSS score of 7.1. A fix is available in version 2026.10.0.
NocoDB versions before 2026.10.1 have a credential exposure vulnerability in the connection-test endpoint. Authorized integration users can manipulate connection parameters to redirect stored credentials to an attacker-controlled server. This allows attackers to capture PostgreSQL md5 or MySQL handshakes, which can be cracked offline to recover database passwords. The vulnerability is rated high severity with a CVSS score of 7.1. A fix is available in version 2026.10.1.
NocoDB versions before 2026.10.1 have an authentication bypass vulnerability due to insufficient session expiration. Attackers holding revoked OAuth access tokens can reuse them via the session header to authenticate as first-party sessions. This bypasses token revocation, client existence checks, route allowlists, and granted resource scopes, enabling unauthorized profile modifications, storage uploads, and forced global sign-outs.
NocoDB versions from 2026.07.0 up to but not including 2026.10.0 contain an SQL injection vulnerability. This flaw allows users with the Creator role to inject SQL commands via unescaped backslashes in the DATETIME_FORMAT formula's format argument on MySQL-backed databases. Exploitation can lead to unauthorized reading of data accessible by the database user, including data outside the intended base. The vulnerability is fixed in version 2026.10.0.
NocoDB versions from 0.253.0 up to but not including 2026.09.1 have an incorrect authorization vulnerability in the baseUserDelete function. This flaw allows users with the Creator role to delete Owners of a base due to a broken role power comparison logic. The vulnerability arises because the function getProjectRolePower returns -1 for the target Owner role and does not block the deletion request. This issue has been fixed in version 2026.09.1.
NocoDB versions before 2026.10.1 have a template injection vulnerability that allows authenticated users with Creator roles to execute arbitrary server-side JavaScript. This occurs via array-form property paths in Handlebars helpers within webhook templates, enabling attackers to bypass prototype guards and execute OS commands or exfiltrate sensitive data.
NocoDB versions before 2026.10.1 have an information disclosure vulnerability due to predictable file paths for data exports. Unauthenticated attackers can reconstruct these paths using table and view metadata to download full data exports, including fields hidden from public views.
NocoDB versions before 2026.10.1 have an incorrect authorization vulnerability that allows organization Creators to access routes restricted to other roles. This flaw arises because the aclFn middleware does not enforce allowedRoles properly. Exploitation can lead to attackers generating super admin password reset links via org-users endpoints, enabling full instance takeover and unauthorized access to read and modify SSO client secrets.
NocoDB versions before 2026.10.1 have a stored HTML injection vulnerability that allows authenticated users with record edit rights to inject malicious HTML content into rich text cells. This content can include spoofed sign-in forms or remote images, which may be used to harvest passwords or disclose viewer IP addresses. The vulnerability arises because the sanitization relies solely on DOMPurify's default policy, which is permissive enough to allow such injections.