NocoDB versions before 2026.10.1 have an authentication bypass vulnerability where OAuth tokens signed with the instance JWT secret can be used to gain full user session privileges. This allows attackers with a narrowly scoped OAuth token to escalate their access by presenting the token to various authentication mechanisms within NocoDB.
NocoDB before 2026.08.0 contains a stored cross-site scripting vulnerability that allows any authenticated user to register OAuth clients with javascript: redirect URIs. Attackers can send a consent link to a signed-in victim so either consent button runs script in the NocoDB origin, stealing the session token for account takeover.
NocoDB versions before 2026.08.0 have an authorization bypass vulnerability in their public shared-view relation endpoints. The flaw allows unauthenticated attackers with a public share link to access child records of filtered-out parent records by supplying guessable auto-incrementing IDs. This bypass occurs because the endpoints verify the existence of a parent record but do not enforce the view's row filters.
NocoDB versions before 2026.08.0 have an authorization bypass vulnerability in public shared-view endpoints. This flaw allows anonymous users holding share links to enumerate sequential primary keys and access records that should be excluded by row filters, including linked data and attachments. The issue is fixed in version 2026.08.0.
NocoDB versions before 2026.07.0 have an SQL injection vulnerability in their MySQL and SQLite clients. Authenticated users with Creator or Owner roles can exploit this by supplying a crafted precision value when creating or updating a column, allowing execution of arbitrary SQL commands against the database.
NocoDB versions prior to 2026.10.0 contain an authorization bypass vulnerability that allows authenticated users with write access to attachment columns to obtain signed download URLs for attachments belonging to other bases. This occurs due to insecure direct object references via user-controlled foreign attachment paths, enabling cross-base file access despite secure attachment mode.
NocoDB versions prior to 2026.08.0 contain a server-side request forgery (SSRF) vulnerability. Authenticated users with base Editor privileges can exploit this flaw by supplying arbitrary URLs to the integration remote fetch operation, enabling backend HTTP requests. This allows attackers to manipulate HTTP method, headers, and body to access internal APIs, loopback services, and cloud metadata endpoints, potentially reading sensitive responses including decrypted integration secrets. The vulnerability is rated high severity with a CVSS 4.0 score of 8.4. A fix is available in version 2026.08.0.
NocoDB versions before 2026.08.0 have an information disclosure vulnerability that allows unauthenticated attackers to access attachments of records excluded by view filters via the shared view attachment-download endpoint. Attackers with a public share link can enumerate sequential primary keys to retrieve signed download paths for files on filtered-out records.
NocoDB versions before 2026.08.0 have an authorization bypass vulnerability in shared-view relation endpoints. The flaw arises because parent-record lookups use only the primary key without applying the view's row filter. This allows anonymous users with share links to enumerate auto-increment primary keys and access linked records that should be filtered out.
NocoDB versions from 2026.06.2 up to but not including 2026.08.0 contain an authorization bypass vulnerability. Authenticated users with base Editor privileges can exploit this flaw to write to data sources that are intended to be read-only by abusing the internal batch endpoint. This allows modification or destruction of records in read-only tables by referencing a writable decoy table in batch operations. The vulnerability is fixed in version 2026.08.0.
NocoDB versions prior to 2026.08.0 contain an insecure direct object reference vulnerability that allows unauthenticated attackers to bypass authorization controls. By supplying arbitrary primary keys, attackers can access records that should be hidden by shared view row filters. This includes the ability to download attachments and enumerate linked records for excluded entries when possessing a share link.
NocoDB versions prior to 2026.08.0 have an authorization bypass vulnerability that allows anonymous users with share links to access records that should be restricted by row filters in shared views. This occurs because the read-by-primary-key access path does not enforce these filters. Exploitation enables attackers to generate signed download URLs for hidden files and access linked-record data via specific routes.
NocoDB versions prior to 2026.08.0 have an information disclosure vulnerability that allows unauthenticated users with a shared-base link to access the base's stored plaintext password via the general base metadata endpoint. This occurs because the password is not stripped from the base read or list responses, enabling attackers to obtain reusable plaintext passwords.
NocoDB versions prior to 2026.04.1 contain a vulnerability where reset password tokens and their expiration timestamps are not cleared after a password change. This flaw allows attackers who possess a still-valid reset link, possibly obtained from prior mailbox access, to reuse the link to reset the password again and regain account control.
NocoDB versions before 2026.08.0 have a stored cross-site scripting (XSS) vulnerability that affects authenticated Creator or Editor users. This flaw allows attackers to inject malicious markup into fields rendered via URL() formulas. The vulnerability arises because the canvas grid renderer assigns unsanitized formula output directly to innerHTML, enabling script execution. Exploitation can lead to theft of session tokens from localStorage and account takeover of users viewing the affected tables.
NocoDB versions prior to 2026.10.1 have a user enumeration vulnerability. Unauthenticated attackers can submit email addresses to the signup endpoint and observe response differences to determine if an email is registered or has a pending Enterprise invitation, even when signup is invite-only. This vulnerability was fixed in version 2026.10.1.
NocoDB versions prior to 2026.08.0 contain an SQL injection vulnerability that allows authenticated users with Creator or Owner roles to execute database functions by using zero-argument function calls as column default values. This can lead to disclosure of sensitive database information such as server addresses, role names, and engine details.
NocoDB versions prior to 2026.08.1 contain a critical authorization bypass vulnerability. Authenticated users with Creator privileges can exploit this flaw to access another tenant's external database by reusing a victim's source ID. This occurs because the NcConnectionMgrv2 component caches connections by the bare source ID, allowing attackers to reflect the victim's cached database schema. Consequently, attackers can read, update, and insert records in the victim's database through their own base models. The vulnerability has a high CVSS 4.0 score of 9.3 and is fixed in version 2026.08.1.
NocoDB versions before 2026.10.1 have a user enumeration vulnerability that allows unauthenticated attackers to identify pending invitees by observing distinct sign-in error messages. This occurs because the authentication service skips password comparison for saltless invited accounts, confirming the existence of an account associated with the email address.
NocoDB versions prior to 2026.09.0 contain an authorization bypass vulnerability that allows authenticated users with Viewer access on one base to access metadata of another base by supplying a manipulated MCP token id in the query string. This flaw enables unauthorized reading of sensitive information such as table lists and member email addresses. The vulnerability is fixed in version 2026.09.0.