NocoDB versions prior to 2026.08.1 contain an authorization bypass vulnerability that allows authenticated users with Creator privileges to access external databases of other tenants. This occurs due to connection caching by source ID, enabling attackers to reuse victim source IDs to access and manipulate another tenant's data.
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 as a result.
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 via script in the Enterprise useGlobal composable without the Secure attribute. This omission allows attackers positioned on the network to capture the session token by observing or inducing plain-HTTP requests to HTTPS instances, enabling session impersonation until the token expires.
NocoDB versions prior to 2026.09.0 have an improper authorization vulnerability that allows users with workspace Creator privileges to read plaintext notification webhook URLs. These URLs include Slack, Teams, Discord, and Mattermost webhooks. An attacker with access can query the webhook plugin listing endpoint to obtain these URLs and then replay them to post arbitrary messages into organization chat channels.
NocoDB versions prior to 2026.09.0 have a server-side template injection vulnerability. Authenticated users with Creator or Owner roles can exploit this flaw by abusing Handlebars webhook helpers to execute arbitrary JavaScript. This allows attackers to invoke the Function constructor and run operating system commands.
NocoDB versions prior to 2026.09.0 contain an authorization bypass vulnerability in the extract-ids.middleware.ts component. This flaw allows authenticated users with Viewer access on one base to use an MCP token ID in the query string to access metadata of another base, including table lists and member email addresses. The vulnerability does not allow modification or denial of service but exposes sensitive information across bases.
NocoDB versions from 0.301.4 up to but not including 2026.10.0 have 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.
NocoDB versions prior to 2026.09.0 contain a critical SQL injection vulnerability that allows authenticated users with Creator or Owner roles to inject raw SQL via a crafted formula. This vulnerability arises from reuse of a parsed_tree without revalidation, enabling attackers to bypass SQLite metadata path protections using an alias. Successful exploitation can escalate privileges to super administrator or allow execution of OS commands on external PostgreSQL hosts.
NocoDB versions prior to 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 handshake data, which can be cracked offline to recover database passwords.
NocoDB versions prior to 2026.10.1 have an information disclosure vulnerability that permits unauthenticated users holding shared view links to access hidden column data. By exploiting the group-by endpoint with specific parameters, attackers can reveal hidden column values, counts, and confirm the existence of such columns.
NocoDB versions prior to 2026.10.0 contain an account takeover vulnerability. Users with the base creator role can exploit this flaw by resending base invitations to generate new invite tokens, which they can then read from the base member list. This allows them to reset the password of other users, including owner or super admin accounts, effectively hijacking those accounts.
NocoDB versions prior to 2026.10.1 contain an SQL injection vulnerability due to improper escaping of backslashes in select-field option titles embedded into MySQL or MariaDB enum/set column definitions. This flaw allows a base creator or owner to manipulate option titles to inject malicious ALTER TABLE statements, potentially modifying database schema elements such as columns and indexes.
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 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.
NocoDB versions prior to 2026.10.0 have an improper access control vulnerability that allows users with Creator roles to exploit internal database flags. By supplying is_meta and is_local flags, attackers can create sources or bases that expose sensitive tables containing user, token, and integration data. This enables unauthorized reading and modification of records, including user roles.
NocoDB versions before 2026.10.1 have a consent phishing vulnerability that permits unauthenticated attackers to register OAuth clients with arbitrary HTTPS redirect URIs via an unauthenticated dynamic client registration endpoint. This flaw allows attackers to impersonate trusted applications on the consent screen without unverified-client warnings or redirect host display, enabling them to obtain tokens that can read and write victim tables and records.
NocoDB versions prior to 2026.10.0 have an information disclosure vulnerability that allows unauthenticated attackers to access hidden column data. By supplying comma-separated group-by column lists, attackers can bypass restrictions on shared view links and retrieve hidden values associated with individual rows.
NocoDB versions prior to 2026.10.1 contain an authentication bypass vulnerability that allows attackers holding revoked OAuth access tokens to authenticate as first-party sessions. This bypass enables attackers to circumvent token revocation, client existence checks, route allowlists, and granted resource scope validations. Exploitation can lead to unauthorized modification of victim profiles, uploading to storage, and forcing global sign-outs.
vLLM versions from 0.6.0 up to but not including 0.33.0 have a vulnerability where the system lacks a request-wide media budget. This allows remote inference clients to submit many remote image URLs in a single request, causing the server to download and decode all images before processing the prompt. This can exhaust frontend resources such as memory, CPU, and network connections, leading to denial of service.
SiYuan versions before 3.8.10 contain a vulnerability where the table block's caption attribute is persisted into IAL properties without proper HTML sanitization. This flaw allows stored cross-site scripting (XSS) upon import or synchronization. An attacker can inject an entity-encoded caption with an onerror handler that executes in the Electron client's nodeIntegration context, potentially leading to remote code execution.
SiYuan versions prior to 3.8.10 have a stored cross-site scripting (XSS) vulnerability in the genAVValueHTML() function. This flaw allows attackers who can store Attribute View asset values to inject malicious scripts via an unescaped image src attribute. The injected script can include a double quote and an onerror handler that executes operating system commands through Node.js in the desktop application when a user opens the affected note or attribute panel.