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 from 2026.07.0 before 2026.10.0 contains an sql injection vulnerability that allows users with Creator role to inject SQL through unescaped backslashes in the DATETIME_FORMAT formula format argument on MySQL-backed bases. Attackers can place a backslash before a quote to terminate the DATE_FORMAT string literal and read any data reachable by the data source's database user, including tables outside the base.
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 before 2026.10.1 contains an incorrect authorization vulnerability that allows organization Creators to reach routes restricted to other roles because the aclFn middleware never enforced allowedRoles. Attackers can generate a super admin password reset link via org-users endpoints to take over the instance, or 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.
NocoDB before version 2026.10.0 contains an SQL injection vulnerability that allows authenticated users with the Creator role to inject malicious SQL during table creation. This vulnerability arises from improper neutralization of special elements in a crafted formula, enabling attackers to escalate privileges to super administrator on SQLite installations.
NocoDB versions prior to 2026.10.1 contain a stored CSS injection vulnerability that allows authenticated users with Commenter or Editor roles to inject inline styles via single quotes in mention text. This injection can manipulate the user interface for other viewers by breaking out of the single-quoted data-id attribute in comments or rich text cells.
vLLM from 0.6.0 before 0.33.0 lacks a request-wide media budget, allowing remote inference clients to exhaust frontend resources by submitting many remote image URLs in one request. Attackers can send a compact request to /v1/messages or /v1/responses that forces downloading and decoding of every image before prompt-length admission, exhausting memory, CPU, and connections.
vLLM versions prior to 0.33.0 contain a path traversal vulnerability that allows malicious actors to redirect model and tokenizer loading by manipulating the verifier.name_or_path field in config.json. This can lead to unauthorized access to local checkpoint directories, exposing tokenizer vocabularies and enabling query access to private models without authentication.
vLLM versions from 0.28.0 up to but not including 0.33.0 have an improper input validation vulnerability. This flaw allows unauthenticated attackers to crash the shared EngineCore by submitting out-of-range prompt token IDs when the service is run with the --skip-tokenizer-init option. Specifically, attackers can send large positive token IDs to certain API endpoints, bypassing vocabulary checks and causing a fatal embedding index error that results in denial of service for all tenants. The issue is fixed in version 0.33.0.
CVE-2026-130683 is a critical path traversal vulnerability in siyuan-note versions before 3.8.10. The application uses an incomplete deny-list for sensitive paths, omitting important shell initialization files and directories. Authenticated administrators can exploit this flaw by calling the /api/file/copyFile endpoint with an absolute path outside the workspace, allowing them to write malicious payloads that execute with user privileges upon the next shell or login. This vulnerability is fixed in version 3.8.10.
SiYuan before 3.8.10 persists a table block's caption attribute into IAL properties without HTML sanitization, causing stored cross-site scripting upon import or sync. Attackers can inject an entity-encoded caption with an onerror handler that executes in the Electron client's nodeIntegration context to achieve remote code execution.
SiYuan note-taking software versions prior to 3.8.10 contain a stored cross-site scripting (XSS) vulnerability due to improper neutralization of input in the renderAVAttribute() function. This vulnerability allows attackers who can set an Attribute View name to inject malicious code that executes OS commands via Node.js when a desktop user opens the affected panel. The issue is an incomplete fix of a previous vulnerability (CVE-2026-44670).
SiYuan versions from 3.3.0 up to but not including 3.8.10 contain a stored cross-site scripting (XSS) vulnerability. This flaw allows attackers to inject malicious HTML through unescaped checkbox column names in the Gallery and Kanban AttributeView renderers. When a crafted .sy.zip document is shared and rendered in the Electron desktop client with nodeIntegration enabled, it can execute arbitrary Node.js and host operating system commands. The vulnerability is rated critical with a CVSS 4.0 score of 9.4. A fix is available in version 3.8.10.
SiYuan note-taking software versions before 3.8.10 contain a stored cross-site scripting (XSS) vulnerability. This flaw allows attackers to inject malicious scripts via Attribute View column names, which are rendered without proper escaping. Exploitation can occur through methods such as addAttributeViewKey, importing .sy.zip files, or synchronization features. When a victim adds or duplicates the malicious column, the injected JavaScript executes with Node.js privileges, enabling desktop code execution. The vulnerability is fixed in version 3.8.10.
SiYuan note-taking software versions before 3.8.10 contain 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 when a user opens the affected note or attribute panel in the desktop application. This vulnerability is critical and has been fixed in version 3.8.10.
Craft CMS versions 5.0.0 through before 5.11.4 have a session management vulnerability related to two-factor authentication (2FA). The flaw allows existing sessions to remain valid even when 2FA is enabled and permits disabling 2FA without requiring re-authentication. An attacker with a hijacked or stale session can maintain full account access and remove 2FA protections silently without needing the password or authentication codes.