CVE Vulnerability Catalog

Trigger.dev from version 4.4.2 to 4.5.0 has a vulnerability in packet presign routes where a caller-controlled filename is passed to generate presigned URLs, allowing directory traversal to escape the object-store prefix and enabling a project API key to read or overwrite another organization's offloaded task payloads on multi-organization self-hosted instances.

Trigger.dev from version 4.4.2 to 4.5.0-rc.5 has a vulnerability in Aws4FetchClient.buildUrl() and presign() where user-controlled packet keys are assigned to URL.pathname, and the route accepts params without rejecting dot segments and without per-resource ownership validation. WHATWG path normalization collapses .. segments before signing, allowing a caller with a valid environment API key to obtain presigned URLs for another tenant's object-store keys and read or overwrite task payloads.

Trigger.dev from version 4.4.2 to 4.5.0-rc.4 has a vulnerability in the POST /api/v1/runs/:runParam/replay endpoint. The database query does not filter by runtimeEnvironmentId, allowing any valid environment API key to replay another tenant's run by friendlyId. Additionally, when payloadType "application/store" is used, payload bytes can be overwritten by an attacker, leading to unauthorized actions.

Russh prior to version 0.62.4 has a denial-of-service vulnerability. An authenticated SSH client can send a pty-req channel request with more than 130 terminal-mode records. The parser in russh/src/server/encrypted.rs stores terminal modes in a fixed 130-entry array but continues increasing the mode count, leading to an out-of-bounds slice and panic before the pty_request handler runs.

dua-cli fails to filter terminal escape sequences when printing marked file paths after exiting the TUI interface. Attackers can craft file names containing OSC/CSI escape sequences that are interpreted by the terminal emulator, enabling title spoofing, clipboard manipulation, or other escape-sequence attacks.

Trix prior to version 2.1.18 is vulnerable to stored cross-site scripting when crafted HTML is pasted into the editor. HTMLParser processes a mock attachment in a <span> with an empty data-trix-attachment="{}" value, causing data-trix-attributes to be applied to a plain string piece. StringPiece.fromJSON accepts an unvalidated href, allowing a javascript: URI to enter the document model and execute when another user renders and clicks the content.

NextAuth.js from 5.0.0-beta.0 until 5.0.0-beta.32 has a vulnerability where applications that gate access by checking only for the existence of the auth object can fail open when Auth.js has a server configuration error. A non-OK session response is parsed into a truthy error object instead of null, so checks such as !!auth evaluate to true for unauthenticated requests.

NextAuth.js prior to @auth/core 0.41.3 and next-auth 4.24.15 and 5.0.0-beta.32 has a vulnerability in the email normalizer, where an address with a fullwidth at-sign (U+FF20) passes validation but after Unicode normalization becomes a standard @, potentially causing the sign-in link to be delivered to an attacker.

JupyterLab from version 3.3.0 to 4.5.10 and 4.6.2 has a vulnerability in notebook settings where sideBySideLeftMarginOverride and sideBySideRightMarginOverride are not properly validated before being inserted into style content. A crafted settings file can contain instructions that execute as code, and importing it or automatic application by an attacker can lead to code execution with the user's access.

JupyterLab from version 4.5.0 to 4.5.10 and 4.6.2 has a vulnerability in the PyPI extension manager. The enforcement of blocked_extensions_uris uses weaker normalization than PyPI package-name canonicalization. An authenticated user can request a PyPI-equivalent spelling such as JupyterLab.Git for a blocklisted package such as jupyterlab-git, bypassing the blocklist.

Budibase prior to 3.39.18 contains a SQL injection vulnerability in the MySQL integration where the table name is not properly escaped in a DESCRIBE statement. An attacker can create a table with a name containing a backtick and stacked statement, which executes during schema discovery by an administrator. Fixed in version 3.39.18.

Budibase prior to 3.39.24 has a vulnerability in the POST /api/public/v1/roles/assign endpoint where appBuilder.appId or role.appId is not validated. An app-scoped builder can grant themselves builder access or arbitrary roles in another app, exposing data, datasource configuration, and automations. Fixed in version 3.39.24.

Budibase prior to version 3.39.25 has a vulnerability in the GET /api/users/metadata and GET /api/users/metadata/:id endpoints. Responses include user objects without removing oauth2.accessToken or oauth2.refreshToken. A user with the POWER role can retrieve identity-provider credentials of SSO-authenticated users and use refresh tokens for persistent access to connected services.

Budibase prior to 3.39.30 has a vulnerability in the OIDC flow, where the email is not verified for email_verified, and accounts are linked based on email. An attacker who can authenticate through an identity provider with an unverified victim email can take over the victim's account and inherit their roles.

streama has an insecure direct object reference vulnerability in ViewingStatusController that allows authenticated users to read and delete other users' viewing status records. Attackers can enumerate all users' watch progress, delete arbitrary viewing history, and manipulate other users' Continue Watching dashboards by supplying arbitrary primary keys without ownership verification.

Budibase before 3.40.0 fails to redact datasource credentials stored in STRING typed fields, allowing authenticated users to read MongoDB connection strings and Firebase private keys in plaintext. Attackers with table read permissions can retrieve datasource configurations via the read API to obtain live backend database credentials and service account keys.

Budibase before 3.40.0 contains an authorization/authentication bypass in the PUT /api/global/users/tenant/owner endpoint. On self-hosted instances, any authenticated user, including a lowest-privilege BASIC app user, can reassign the tenant account-holder email to an attacker-controlled address. The attacker can then use the public password-reset flow to take over the admin account, leading to full administrative access.

Budibase before 3.40.0 contains server-side request forgery vulnerabilities in OpenAPI query import and REST query execution that allow authenticated builder-level users to bypass DNS pinning protections through DNS rebinding attacks. Attackers can configure hostnames that resolve to public addresses during validation but to loopback or private addresses during actual connection, allowing access to blocked internal HTTP services.

Budibase before 3.40.0 contains a SQL injection vulnerability in the Oracle datasource connector's post-write row lookup that fails to escape table names in identifiers. Attackers with write permission on a table with a double-quote in its name can inject SQL that executes as the datasource's database user to read or modify arbitrary data.

Budibase before 3.40.0 contains an unauthenticated SQL injection vulnerability in webhook-triggered automations with EXECUTE_QUERY steps. Attackers can POST attacker-controlled JSON to the webhook trigger endpoint to inject SQL payloads that execute with builder-configured database credentials, enabling data exfiltration, modification, and persistence in connected datasources.