Vikunja versions from 0.8.0 up to but not including 2.8.0 contain a denial of service vulnerability. Authenticated project readers can exploit this by sending CalDAV PROPFIND requests with repeated calendar-data properties, causing excessive resource consumption. This can exhaust server memory, CPU, and bandwidth, leading to service disruption. The vulnerability is fixed in version 2.8.0.
Vikunja versions from 2.2.1 up to but not including 2.8.0 contain a vulnerability in the TOTP validation process that allows attackers to bypass replay protection by padding consumed one-time passcodes with whitespace. An attacker with valid credentials who observes a used TOTP code can reuse it with added whitespace within the validity window to gain a session token.
Vikunja versions from 0.16.0 up to but not including 2.8.0 contain a vulnerability where users' Trello API tokens are written to application logs and Sentry. This occurs because provider errors are formatted verbatim in listeners.go, exposing tokens embedded in URL error messages during Trello migration failures. The vulnerability allows anyone with access to logs or telemetry data to obtain these reusable third-party credentials. The issue is fixed in version 2.8.0.
Vikunja versions 2.3.0 through 2.7.x contain a vulnerability in the CSV migration module where memory allocation is uncontrolled due to lack of de-duplication of label column mappings and no cap on labels per row. Authenticated users can exploit this by sending a specially crafted request to the migration endpoint, causing the server to exhaust memory and potentially crash.
Vikunja versions from 0.20.5 up to but not including 2.8.0 have a login cross-site request forgery (CSRF) vulnerability in the OpenID Connect callback component. This flaw allows attackers to craft a callback link with an empty state parameter and their own authorization code, which can silently log victims into the attacker's account and expose victim-entered data. The vulnerability is fixed in version 2.8.0. The CVSS 4.0 score is low (2.3), reflecting limited impact and attack complexity.
Vikunja versions from 0.17.0 up to but not including 2.8.0 have an incorrect authorization vulnerability. When a task is deleted, the notification and webhook payload include related tasks with the deleting user's permissions but are sent to all project subscribers without checking each recipient's authorization. This allows subscribers or webhook owners to receive full data of related tasks in private projects they normally cannot access.
Vikunja versions from 2.2.0 up to but not including 2.8.0 have an information disclosure vulnerability. Authenticated users can exploit the tasks.overdue webhook to access private project details of other users, including project titles, descriptions, and owner IDs. This occurs by registering a personal tasks.overdue webhook with a subscribed overdue task, which then leaks sensitive information to external URLs. The vulnerability is fixed in version 2.8.0.
Vikunja versions from 0.14.0 up to but not including 2.8.0 have a mass assignment vulnerability allowing authenticated users to modify JSON-hidden fields via XML request bodies to the v1 API. This flaw permits attackers to set sensitive attributes such as BackgroundFileID to download stored files or IsAdmin to create bots with administrative privileges. The vulnerability is fixed in version 2.8.0.
Vikunja versions from 1.0.0 up to but not including 2.8.0 have an account takeover vulnerability related to improper authentication. Attackers can hijack Single Sign-On (SSO) identities by creating local accounts with unverified victim emails when the email fallback feature is enabled. This causes the victim's first OpenID Connect (OIDC) login to link to the attacker-controlled account, exposing the victim's data. The issue is fixed in version 2.8.0.
OpenRemote core versions from 1.2.0 up to but not including 1.34.0 have an authorization bypass vulnerability in the AlarmFacade component. This flaw allows users with write:rules permission to create alarms for assets outside their authorized ruleset subtree. Exploitation involves deploying a JSON asset-scoped ruleset with crafted asset IDs to generate high severity alarms and trigger operator notifications for arbitrary assets within the realm. The vulnerability has a medium severity score of 5.3 and was fixed in version 1.34.0.
OpenRemote core versions before 1.34.0 have an authentication bypass vulnerability in the UserAssetProvisioningMQTTHandler component. This flaw allows unauthenticated attackers to impersonate provisioned devices by publishing a known device's public certificate to the provisioning request topic. Exploiting this, attackers can authenticate their MQTT connection as the device's service account, enabling them to read and modify assets without possessing the device's private key. The vulnerability is rated critical with a CVSS score of 9.2 and was fixed in version 1.34.0.
SurrealDB versions 3.0.0 up to but not including 4.0.0 have an authorization bypass vulnerability. This flaw allows clients with table write access to persist writes that should be refused by throwing table events within interactive transactions. Attackers can execute guarded statements via RPC begin and query, ignore the resulting error, and commit the transaction to persist unauthorized records and side effects.
SurrealDB versions from 1.0.0 up to but not including 4.0.0 have a vulnerability where the CLI commands print sensitive environment variables SURREAL_PASS and SURREAL_TOKEN in clear text in their help output. This exposure can reveal root database credentials if the terminal output is logged or shared. The issue is fixed in version 4.0.0.
SurrealDB versions from 2.2.0 up to but not including 4.0.0 have a vulnerability where error messages generated during a failed delete operation reveal the record IDs of referencing rows. This occurs when a delete is blocked by an ON DELETE REJECT reference, and the system does not verify the caller's SELECT permission on those referencing rows. An authenticated user with DELETE permission can exploit this to discover the existence and exact IDs of records that should be hidden by row-level SELECT permissions. The issue is fixed in SurrealDB 4.0.0.
SurrealDB versions 3.0.0 up to but not including 4.0.0 contain a path traversal vulnerability in the filesystem storage bucket. This flaw arises because the system only canonicalizes the bucket root directory, failing to properly resolve descendant symbolic links. An attacker can exploit this by referencing paths through existing symlinks inside the bucket, bypassing lexical prefix checks and enabling unauthorized reading and writing of files across the host filesystem. The vulnerability is addressed in SurrealDB version 4.0.0.
SurrealDB versions from 1.0.0 up to but not including 4.0.0 contain a critical vulnerability where the embedded JavaScript engine bypasses authorization checks. Authenticated users who are denied access to certain built-in SurrealQL functions can still execute these functions by invoking them through the surrealdb.functions bridge, which does not enforce capability checks. This flaw is fixed in version 4.0.0.
SurrealDB versions 3.1.0 up to but not including 4.0.0 contain an SQL injection vulnerability in the Model Context Protocol (MCP) server. The flaw arises because the identifier validator mishandles escaped backticks, allowing attackers to break out of quoted identifiers and execute arbitrary SurrealQL commands. This vulnerability has a high severity score of 8.8 and is fixed in version 4.0.0.
SurrealDB versions 3.0.0 up to but not including 4.0.0 have a path traversal vulnerability in the bucket storage layer on Windows. The vulnerability arises because the pathname validation splits object keys only on forward slashes, while the file path conversion treats backslashes as directory separators. This discrepancy allows attackers to craft object keys that bypass traversal checks and access or modify files in other buckets.
SurrealDB versions 3.0.0 up to but not including 4.0.0 have a path traversal vulnerability in the direct filesystem buckets feature. The vulnerability arises because the access control checks are performed on un-normalized keys, while the filesystem path normalization allows traversal sequences like '..' to escape the intended directory. An authenticated tenant with limited key permissions can exploit this to access, modify, or delete arbitrary files within the storage root by supplying crafted keys such as /public/../private/confidential.txt. This issue is fixed in SurrealDB 4.0.0.
SurrealDB versions 3.0.0 up to but not including 4.0.0 have an authorization bypass vulnerability. Authenticated users with the read-only VIEWER role can create new schemaless tables in non-STRICT mode databases without proper permission checks. This occurs because CREATE statements on nonexistent tables implicitly define them without requiring the DEFINE TABLE permission. The vulnerability allows VIEWER users to clutter the database schema or cause naming collisions with application tables.