ArcadeDB versions from 26.3.1 up to but not including 26.11.1 contain a vulnerability that allows server administrators to bypass read-only restrictions in the MCP query tool. This occurs because Groovy-fallback Gremlin scripts that perform write operations are incorrectly classified as read-only, enabling unauthorized data modifications. The issue is fixed in version 26.11.1.
ArcadeDB versions before 26.11.1 have a denial of service vulnerability in the Redis protocol handler. The handler fails to respond to or close pre-authentication connections when receiving malformed arrays, allowing unauthenticated attackers to hold connections open indefinitely and exhaust server resources.
ArcadeDB versions before 26.11.1 have an authorization bypass vulnerability allowing authenticated users to read schema definitions of types they are denied access to. This occurs because listings ignore per-type access control lists (ACLs). Attackers can exploit this by querying the PostgreSQL wire catalog, GraphQL introspection, or MCP get_schema to obtain detailed schema information such as property names, indexes, inheritance, and materialized view SQL.
ArcadeDB versions from 26.2.1 up to but not including 26.11.1 have a vulnerability where the system reveals whether a database exists or not before authorization, allowing authenticated users to enumerate database names they are not authorized to access. Additionally, a failed Bolt LOGON leaves the previous user principal bound after a RESET command. This issue has a CVSS 4.0 score of 7.1 (high severity) and is fixed in version 26.11.1.
ArcadeDB versions from 26.7.1 up to but not including 26.11.1 have an information disclosure vulnerability. The issue arises because the LSMTreeFullTextIndex component computes BM25 corpus statistics across all buckets of an indexed type without enforcing bucket access controls on subtypes. This allows authenticated users with read access to a supertype but not its subtypes to execute EXPLAIN or PROFILE commands on full-text queries and infer information about hidden subtype documents.
ArcadeDB versions from 21.10.1 up to but not including 26.11.1 have a resource-limit bypass vulnerability. This flaw allows restricted users to bypass per-group readTimeout limits by exploiting shared cached SQL statements and plans. Attackers can execute SQL queries cached by unrestricted users to avoid timeout restrictions or impose their own timeout and limits on privileged users such as root.
ArcadeDB native-image server builds from version 26.8.1 up to but not including 26.11.1 contain an authorization bypass vulnerability. This flaw allows authenticated clients to perform write operations through read-only query paths by nesting statements within SELECT queries. The vulnerability arises due to missing reflection metadata causing the SQL AST inspector to have an empty abstract syntax tree, enabling INSERT statements in projections or LET clauses to persist via various query endpoints and modes.
ArcadeDB versions from 25.8.1 up to but not including 26.11.1 have an incorrect authorization vulnerability. This flaw arises because per-type ACLs are keyed by type name, but renames are not propagated to permission configurations. Authenticated users with only updateSchema privileges can exploit this by running ALTER TYPE NAME on a denied type to gain unauthorized read, DELETE, and TRUNCATE access. The unauthorized access is immediate for TIMESERIES types and delayed until the next security rebuild for record-backed types. The vulnerability has a high severity with a CVSS 4.0 score of 8.7. A fix is available in version 26.11.1.
ArcadeDB versions from 26.11.1-SNAPSHOT up to but not including 26.11.1 contain an authorization bypass vulnerability. This flaw allows authenticated users to bypass per-type access control checks when opening a database on demand. Specifically, an attacker can send a POST request to a closed database to perform unauthorized read and write operations on types they should not have access to. The vulnerability is addressed in version 26.11.1.
A denial of service vulnerability exists in actix-http versions 3.0.0 up to but not including 3.20.3. It allows unauthenticated remote attackers to exhaust server memory by sending specially crafted Brotli-compressed request bodies with large window sizes, causing excessive memory allocation and potential server crashes.
actix-http versions from 3.18.10 up to but not including 3.20.2 contain an HTTP request smuggling vulnerability in the chunked decoder. The flaw arises because the decoder incorrectly treats a bare LF after the last chunk as the start of a trailer section. This allows attackers to craft a request body ending with 0\r\n\n that can cause the next request's body to be parsed as new requests when passing through a connection-reusing proxy, potentially bypassing WAF or upstream protections.
actix-files versions before 0.7.4 contain an information disclosure vulnerability that allows remote unauthenticated attackers to read hidden files by exploiting Windows 8.3 short-name aliases. This bypasses the leading-dot check designed to protect sensitive files such as .env and .git directories, potentially exposing secrets and configuration data.
Rclone versions from 1.56.0 up to but not including 1.76.0 have a timing side-channel vulnerability in the htpasswd authentication middleware. This flaw allows unauthenticated attackers to enumerate valid usernames by sending HTTP Basic Auth requests with incorrect passwords and measuring response times. The vulnerability arises because bcrypt verification is only performed for existing users, causing observable timing discrepancies. The issue is fixed in version 1.76.0.
CVE-2026-134349 is a memory exhaustion vulnerability in rclone versions 1.46.0 up to but not including 1.76.0. The flaw exists in the remote control server where unauthenticated clients can send oversized JSON payloads to protected RC methods. The server decodes these payloads before performing authorization checks, which can lead to out-of-memory termination and disrupt ongoing transfers.
rclone versions 1.67.0 through 1.75.x contain a vulnerability in the Ulozto backend where authentication tokens are leaked to unintended hosts during HTTP redirects. This occurs because the downloads use an authenticated client instead of a CDN client, exposing long-lived API keys and session tokens. An attacker able to observe or redirect CDN download traffic could capture these tokens and gain persistent access to the victim's Ulozto storage.
Rclone versions from 1.49.0 up to but not including 1.76.0 have an authentication vulnerability where revoked users can retain access by reconnecting within five minutes due to cached authentication responses not being revalidated. This affects the serve sftp, ftp, http, and webdav features. The issue is fixed in version 1.76.0.
Rclone versions from 1.51.0 up to but not including 1.76.0 contain an authentication bypass vulnerability in the serve sftp --auth-proxy feature. The vulnerability arises because the cache key used for authentication does not include the authentication method, allowing attackers who know a victim's base64 public key to reuse cached authentication entries from the same client IP and gain unauthorized read-write access to the virtual file system (VFS). This flaw has been fixed in version 1.76.0.
rclone versions prior to 1.76.0 have a vulnerability where credentials are leaked in the swift, netstorage, and seafile backends due to insecure handling of HTTP redirects. This can expose authentication tokens or passwords to unauthorized actors if they intercept or observe redirects from the configured endpoints.
CVE-2026-134354 is a vulnerability in rclone versions 1.59.0 up to but not including 1.76.0. It involves improper link resolution in the local backend's setXattr function, allowing attackers to escape confinement by writing user.* extended attributes outside the intended destination root via a maliciously planted symlink. This can be exploited using the --links and --metadata options to set attacker-controlled extended attributes on files outside the target directory.
CVE-2026-134355 is an improper authorization vulnerability in AzuraCast versions before 0.24.1. It affects the /api/station/{station_id}/profile/edit endpoint, allowing authenticated station users with Manage Station Profile permission—but without Manage Station Broadcasting permission—to access and modify sensitive Icecast/Shoutcast passwords. This includes admin, source, relay, and streamer passwords. Exploitation can lead to unauthorized reading or overwriting of these passwords, potentially locking out legitimate operators.