Huginn versions before 2026.11.09 have an information exposure vulnerability in the JqAgent component. Authenticated users who can create, configure, or dry-run a JqAgent may exploit this flaw to read the server process environment. This occurs because the jq child process inherits the environment, allowing attackers to disclose sensitive secrets such as APP_SECRET_TOKEN, database credentials, SMTP, and OAuth secrets.
OpsTree BuildPiper versions prior to 2.7.0 have a path traversal vulnerability that allows authenticated users with build configuration permissions to read arbitrary files on the build worker. This is achieved by supplying unvalidated dockerfile_path and build context values, enabling attackers to specify traversal or absolute paths such as /etc/passwd. The file contents are then disclosed in the build log when a build is triggered.
OpsTree BuildPiper versions before 2.7.0 have an improper authorization vulnerability that allows authenticated deploy users to define arbitrary Kubernetes hostPath volumes without restrictions. This flaw enables attackers to mount the worker node root filesystem with read-write access, breaking container isolation and potentially leading to node and cluster compromise.
OpsTree BuildPiper versions before 2.7.0 have a critical privilege escalation vulnerability. Project users can exploit the Additional Manifest feature to submit unrestricted Kubernetes manifests. This allows attackers to create a ClusterRoleBinding that grants cluster-admin rights to a service account. The pipeline applies these manifests with cluster-wide credentials, enabling full control over all workloads and secrets in the Kubernetes cluster.
OpsTree BuildPiper versions prior to 2.7.0 contain a path traversal vulnerability that allows authenticated users to read arbitrary files by supplying traversal sequences in Additional Manifest file paths. This can lead to exposure of sensitive files such as configuration files and service-account tokens embedded in generated manifests and logs.
OpsTree BuildPiper versions prior to 2.7.0 have an authorization bypass vulnerability. Authenticated users can exploit this flaw by supplying a foreign project_env_id to attach another application's environment to their service. This allows attackers to configure continuous integration (CI) pipelines and trigger builds and deployments using the victim application's configuration, registries, and deployment infrastructure.
OpsTree BuildPiper versions before 2.7.0 have a broken access control vulnerability that allows authenticated users to list and build from Git repositories restricted to other projects. This flaw enables attackers to enumerate repositories via a specific API endpoint and clone source code, manifests, and committed secrets from projects they should not have access to.
A server-side request forgery (SSRF) vulnerability exists in Huginn versions from 2026.09.09 up to but not including 2026.11.09. The flaw arises because the egress proxy configuration applies only to certain HTTP clients (Faraday and Typhoeus), allowing authenticated users to exploit other HTTP clients (HTTParty, open-uri, Net::HTTP) to send requests directly to internal services. This can lead to exposure of internal data via the JiraAgent, which returns response data as events.
OpsTree BuildPiper versions prior to 2.7.0 have a vulnerability in the password-reset OTP verification process due to the absence of rate limiting. This allows unauthenticated attackers to brute force 6-digit OTP codes by repeatedly submitting guesses to the check_otp endpoint. Successful exploitation enables attackers to reset the target user's password and take over their account.
Teable versions before 2026-10-12T12-45-53Z.3331 contain a stored cross-site scripting (XSS) vulnerability. Authenticated users can upload SVG or HTML attachments with attacker-chosen content types, enabling script execution in the context of the victim's session. This vulnerability allows attackers to perform API actions via the same-origin /api/attachments/read URL, which is served inline with an empty Content-Security-Policy.
Glance versions from 0.8.0 up to but not including 0.8.8 have a vulnerability where unauthenticated attackers can enumerate configured page slugs by observing differences in HTTP response codes. This occurs due to discrepancies in the handlePageRequest and handlePageContentRequest endpoints, allowing attackers to distinguish valid page names from invalid ones based on 303/401 versus 404 status codes.
Ryot versions prior to 10.5.6 have an authorization bypass vulnerability that allows authenticated users to delete entries from other users' collections by manipulating collectionName and creatorUserId parameters. User IDs can be enumerated via the usersList query, enabling targeted deletion of collection entries such as those in the Watchlist collection.
Glance versions from 0.7.9 up to but not including 0.8.8 contain a stored cross-site scripting (XSS) vulnerability. This flaw allows malicious extension endpoints to inject javascript: URLs via the Widget-Title-URL response header. When users click the widget title, the injected script executes, enabling attackers to read dashboard pages through same-origin requests and exfiltrate content. The vulnerability has a CVSS score of 4.7, indicating medium severity.
Cudy TR3000 devices running firmware versions before 2.5.42 have an OS command injection vulnerability. This flaw allows a malicious or compromised Auto Configuration Server (ACS) to execute arbitrary commands as root by sending a specially crafted SetParameterValues request with shell metacharacters in the User.Username parameter. The vulnerability arises because the username value is passed without validation to an os.execute() call in the device's Lua script, leading to root-level command execution.
Zipline versions prior to 4.5.0 have an insecure direct object reference vulnerability due to missing ownership verification in the PATCH and DELETE API handlers for user folders. Authenticated attackers can manipulate folder IDs belonging to other users to rename, make public, enable uploads, or delete those folders.
Zipline versions before 4.5.0 have a stored open redirect vulnerability that allows authenticated users to create short URLs redirecting to arbitrary destinations, including potentially malicious javascript: URIs. This flaw arises from missing scheme validation in the POST /api/user/urls endpoint. Exploitation could lead visitors of trusted short links to phishing or malware sites.
Zipline versions through 4.4.0 have a path traversal vulnerability that allows authenticated attackers to delete arbitrary server files. This is achieved by injecting traversal sequences via the x-zipline-file-extension header. The attack involves uploading a file with a specially crafted stored name and short expiry, causing the LocalDatasource deletion process to remove chosen files, potentially leading to denial of service or data loss.
Zipline versions through 4.4.0 have a path traversal vulnerability that allows authenticated users to read arbitrary files on the server. This occurs by exploiting a fallback mechanism where the :id parameter in the GET /api/user/files/:id/raw endpoint is treated as a datasource key. Attackers can use encoded traversal sequences to escape the intended uploads directory and access sensitive files such as /etc/shadow.
Zipline versions through 4.4.0 have an authentication bypass vulnerability in the WebAuthn login endpoint. This flaw allows attackers who know a registered credential ID to create sessions without verifying the assertion, enabling impersonation of the associated account. Exploitation can lead to administrative control over SUPERADMIN accounts.
Zipline versions through 4.4.0 have a path traversal vulnerability in the PATCH /api/user/files/:id rename endpoint. Authenticated users can exploit this flaw by supplying crafted file names that bypass database uniqueness checks but are normalized by the system, allowing overwriting of existing uploaded files.