Kah-Ja

**Name of the Vulnerable Software and Affected Versions** Trilium versions prior to 0.104.0 **Description** The automatic image-download feature fails to validate paths when processing `file://` URLs within `img` tags of a note. This allows an authenticated user to disclose arbitrary files readable by the process by saving a text note with a source like `file:///etc/passwd`, which the system then stores as a note attachment. Additionally, targeting an unbounded source such as `/dev/zero` can lead to uncontrolled memory allocation, resulting in a server process crash. This functionality is enabled by default and accessible via the web UI, the ETAPI, the web clipper, and note imports, requiring an authenticated session or an ETAPI token. **Recommendations** Update to version 0.104.0.

**Name of the Vulnerable Software and Affected Versions** Adminer versions 5.3.0 through 5.4.2 **Description** An arbitrary file write issue exists when the sql-log plugin is enabled. An authenticated user can utilize path traversal sequences—a technique used to access files and directories outside the intended folder—via the `ns` parameter in the 'plugins/sql-log.php' endpoint to write arbitrary .sql files with controlled content to any writable directory on the host. **Recommendations** Update Adminer to a version later than 5.4.2. As a temporary mitigation, disable the sql-log plugin or restrict access to the `ns` parameter in the 'plugins/sql-log.php' endpoint.

**Name of the Vulnerable Software and Affected Versions** Typebot versions prior to 3.18.0 **Description** The server-side Send Email integration block allows arbitrary reading of local files on the server. The issue occurs because the `parseAttachments` helper returns a supplied value as a filesystem path if it does not start with the application's base URL, rather than enforcing an http or https URL. Since the Nodemailer transport is initialized without `disableFileAccess` or `disableUrlAccess` enabled, an absolute server path provided via a typebot variable is read from the local filesystem and sent as an attachment. A registered user can exploit this by publishing a bot that attaches sensitive files, such as `/etc/passwd` or `/proc/self/environ`, and sends them to a controlled email address. This allows the retrieval of process environment secrets, including the database connection string and credential encryption key, without requiring administrative privileges or victim interaction. **Recommendations** Update to version 3.18.0.

**Name of the Vulnerable Software and Affected Versions** Typebot versions prior to 3.18.0 **Description** Self-hosted installations using default passwordless email magic-link authentication are susceptible to login-code brute forcing, which can lead to account takeover. The system replaces the standard cryptographically secure token with a 6-digit code generated via `Math.random()`, limiting the keyspace to 900,000 possibilities with a 10-minute expiration. The verification callback lacks attempt limits, lockout mechanisms, and CSRF (Cross-Site Request Forgery) protection. Furthermore, incorrect guesses do not invalidate the actual code. The existing rate limiter for sending codes relies on the `X-Forwarded-For` header, which is client-controlled, allowing an attacker to request multiple concurrent codes for a single victim to increase the probability of a successful guess. An attacker knowing a victim's email can gain an authenticated session and full access to bots, results, and integration credentials without user interaction. Deployments using only OAuth or SSO are not affected. **Recommendations** Update to version 3.18.0.

**Name of the Vulnerable Software and Affected Versions** SurrealDB versions prior to 3.1.5 **Description** An arbitrary file read issue exists in the DEFINE ANALYZER mapper filter. Database users with EDITOR or OWNER roles can read files accessible to the SurrealDB process by specifying arbitrary file paths in the mapper filter. The file contents are then retrieved through query error messages, provided that the `SURREAL FILE ALLOWLIST` variable is empty or not configured. **Recommendations** Update SurrealDB to version 3.1.5 or later. Configure the `SURREAL FILE ALLOWLIST` variable to restrict file access.

**Name of the Vulnerable Software and Affected Versions** Kestra versions prior to 1.0.45 Kestra versions prior to 1.3.21 **Description** The authentication filter for the REST API `@Filter("/api/v1/**")` incorrectly treats any request path ending in `/configs` as a public instance-config endpoint, allowing requests to bypass Basic-Auth. This occurs because the platform identifies resources via caller-chosen URL path segments, such as `/api/v1/{tenant}/flows/{namespace}`, `/api/v1/{tenant}/executions/{namespace}/{id}`, and `/api/v1/{tenant}/namespaces/{namespace}/kv/{key}`. By using `configs` as the final segment, an unauthenticated user can access the flow-create and execution-trigger routes to create and run a flow containing a Shell or Process task. These tasks execute as root within the container, and since the official docker-compose.yml mounts `/var/run/docker.sock`, the attacker can gain access to the host Docker daemon. **Recommendations** Update Kestra to version 1.0.45 or later. Update Kestra to version 1.3.21 or later.

**Name of the Vulnerable Software and Affected Versions** Budibase versions prior to 3.39.9 **Description** An issue exists where a workspace-level builder can read any file the server process has access to by uploading a specially crafted PWA zip file. The `POST /api/pwa/process-zip` endpoint extracts the uploaded zip using a library that preserves absolute symbolic links. The system's icon-source validator fails to reject these symbolic links, allowing a file stored within the base directory to point to sensitive system files. Subsequently, the server opens the resolved path and streams the bytes into MinIO, which are then served back to the user via the `GET /api/assets/{appId}/pwa/{uuid}.png` endpoint. In default Docker deployments where the server runs as root, this can lead to the disclosure of critical files such as `/etc/shadow` and `/data/.env`, which contains sensitive credentials like `JWT SECRET`, `INTERNAL API KEY`, and `DATABASE URL`. **Recommendations** Update Budibase to version 3.39.9 or later.

**Name of the Vulnerable Software and Affected Versions** Budibase server versions prior to 3.39.1 **Description** An issue exists where the `enrichContext` function substitutes parameter values into the raw JSON body of a query and then parses the result using `JSON.parse`. The `validateQueryInputs` function fails to escape JSON metacharacters such as `"`, ``, and `}`, only rejecting Handlebars markers. This allows an attacker to inject closing quotes and additional keys, lifting attacker-controlled fields into the parsed filter object. For MongoDB `find` operations, the parsed filter is passed directly to `collection.find()`, allowing an attacker to override filters and return every document in a collection. Similarly, against `updateMany` queries, the filter scope can be widened to the entire collection, causing the `$set` body to run against every matched document. The `authorized` middleware skips authentication and CSRF checks when a query's role is set to `PUBLIC`. Consequently, an unauthenticated visitor can use the `POST /api/v2/queries/:queryId` endpoint, providing only a public `x-budibase-app-id` header, to read or modify every document in backing MongoDB, CouchDB, Elasticsearch, DynamoDB-PartiQL, or REST-with-JSON-body collections. **Recommendations** Update Budibase server to a version later than 3.39.0. As a temporary workaround, avoid setting the role of non-SQL queries (MongoDB, CouchDB, Elasticsearch, DynamoDB-PartiQL, or REST with `bodyType=json`) to `PUBLIC` until the update is applied.

**Name of the Vulnerable Software and Affected Versions** NocoDB versions prior to 2026.05.1 **Description** The shared form-view submit handler in `packages/nc-gui/composables/useSharedFormViewStore.ts` fails to validate the URL scheme when writing the `redirect url` to `window.location.href`. While a same-host check is performed, non-network schemes such as `javascript:`, `data:`, `vbscript:`, and `file:` result in an empty host string, causing the application to treat the URL as an external redirect and execute it within the NocoDB origin. A user with an `editor` role or higher can inject a `javascript:` URL into the `redirect url` via the form-view PATCH endpoint. When an authenticated viewer submits the form through a shared link, the payload executes, allowing the attacker to read the session token from `localStorage["nocodb-gui-v2"]` and perform actions using the viewer's identity. **Recommendations** Update to version 2026.05.1. As a temporary workaround, restrict users with the `editor` role from modifying the `redirect url` in form views until the update is applied.

**Name of the Vulnerable Software and Affected Versions** authentik versions prior to 2025.12.5 authentik versions prior to 2026.2.3 **Description** An issue exists in the Simple Flow Executor (SFE), which is a component used to manage the sequence of steps in an authentication flow. Due to the implementation of stages designed to maintain compatibility with legacy browsers, a cross-site scripting (XSS) flaw is present in the `AutosubmitStage` function. XSS is a type of security flaw that allows an attacker to inject malicious scripts into web pages viewed by other users. **Recommendations** Update to version 2025.12.5. Update to version 2026.2.3.