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 before 2026.08.0 contains a server-side request forgery vulnerability that allows authenticated base Editors to make backend HTTP requests by supplying arbitrary URLs to the integration remote fetch operation. Attackers can control the method, headers, and body to reach internal APIs, loopback services, and cloud metadata endpoints, reading responses and echoed decrypted integration secrets.
NocoDB before 2026.08.0 contains an information disclosure vulnerability that allows unauthenticated attackers to access attachments of filtered-out records through the shared view attachment-download endpoint. Attackers holding a public share link can enumerate sequential primary keys to obtain signed download paths for files on records the view's row filter excludes.
NocoDB before 2026.08.0 contains an authorization bypass in shared-view relation endpoints because parent-record lookups apply only the primary key, not the view's row filter. Anonymous share-link holders can enumerate auto-increment primary keys against the has-many, many-to-many, one-to-many and link-to-another-record routes to read linked records of filtered-out rows.
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 before 2026.08.0 contains an insecure direct object reference vulnerability that allows unauthenticated attackers to access records hidden by a shared view's row filter by supplying arbitrary primary keys. Attackers with the share link can request attachment downloads and many-to-many or has-many link listings for excluded records to obtain their attachment files and linked record identities.
NocoDB before 2026.08.0 contains an authorization bypass vulnerability that allows anonymous share link holders to access records excluded by a shared view's row filter, because the read-by-primary-key path ignores the view's filters. Attackers can request the public attachment-download or nested-link listing routes with a record id to mint signed download URLs for hidden files and read linked-record data.
NocoDB before 2026.08.0 contains an information disclosure vulnerability that allows unauthenticated shared-base link holders to read the base's stored plaintext password through the general base metadata endpoint. Attackers with a share link can query the base read or list responses in bases.controller.ts, which skip password stripping in sanitizeBase.ts, 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 before 2026.08.0 contains a stored cross-site scripting vulnerability that allows authenticated Creator or Editor users to execute script by injecting markup into fields rendered through URL() formulas. The canvas grid renderer assigns unsanitized formula output to innerHTML, letting attackers steal session tokens from localStorage and take over accounts of users viewing the table.
NocoDB before 2026.10.1 contains a user enumeration vulnerability that allows unauthenticated attackers to determine registered email addresses by observing differing sign-up endpoint responses. Attackers can submit addresses to signup in users.service.ts and compare error messages to identify existing accounts and pending Enterprise invitations, even under invite-only signup.
NocoDB before 2026.08.0 contains an sql injection vulnerability that allows authenticated Creator or Owner users to execute database functions by supplying zero-argument function calls as column default values. Attackers can plant functions like version() or inet_server_addr() in PostgreSQL or MySQL column definitions and read results through record APIs, disclosing server addresses, role names, and engine details.
NocoDB before 2026.08.1 contains an authorization bypass vulnerability that allows authenticated Creators to access another tenant's external database by reusing a victim source id when adding a source. Because NcConnectionMgrv2 caches connections by bare source id, attackers can reflect the victim's cached database schema and read, update, and insert records through their own base models.
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 before 2026.09.0 contains an authorization bypass vulnerability in extract-ids.middleware.ts that allows authenticated users to resolve roles against another base by supplying an MCP token id in the query string. Attackers with Viewer access on one base can mint an MCP token and pass its id to read another base's metadata, including table lists and member email addresses.
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 before 2026.09.0 contains an sql injection vulnerability that allows authenticated Creator or Owner users to inject raw SQL by persisting a crafted formula parsed_tree reused without revalidation. Attackers can bypass the SQLite metadata path guard with an alias to plant the tree, escalating to super administrator or executing OS commands on external PostgreSQL hosts.
NocoDB from 0.301.4 before 2026.10.1 writes the nc_token session cookie from script in the Enterprise useGlobal composable without the Secure attribute. Network-positioned attackers can observe or induce plain-HTTP requests to https instances to capture the session token and impersonate the victim until expiry.