AzuraCast versions prior to 0.24.1 contain a vulnerability where backslashes in Liquidsoap annotation values are not properly escaped. This flaw allows media managers to break out of quoted annotation strings by crafting an ID3 title ending with a backslash, enabling injection of a process: protocol URI. Successful exploitation results in OS command execution within the Liquidsoap container during media playback.
Coder versions 2.6.0 before 2.29.21, 2.30.0 before 2.34.10, 2.35.0 before 2.35.8, 2.36.0 before 2.36.5, and 2.37.0 before 2.37.1 contain a denial of service vulnerability in the workspace agent dRPC API. The vulnerability arises because handlers dereference unset request sub-messages and unconfigured Tailnet providers without recovering from panics. An attacker with a workspace agent token can exploit this by sending specific malformed messages to repeatedly crash the coderd process.
rclone versions before 1.76.0 have a vulnerability in the swift, netstorage, and seafile backends where credentials can be leaked due to following HTTP redirects with Go's default policy. This causes authentication headers, passwords, or API tokens to be sent on redirects that downgrade from HTTPS to HTTP or cross-host redirects, potentially exposing sensitive credentials to attackers who can observe or receive these redirects.
Rclone versions from 1.51.0 up to but not including 1.76.0 have 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. This enables unauthorized read-write access to the virtual file system (VFS).
Coder versions 2.32.0 before 2.34.17, 2.35.0 before 2.36.12, 2.37.0 before 2.37.9, and 2.38.0 before 2.38.5 contain a symlink-following vulnerability in the Coder Agents read_skill_file tool. This flaw allows attackers who place a malicious skill with a symlinked supporting file in a victim's workspace to leak files outside the intended skill directory into the model context and chat history. The vulnerability arises because the tool validates skill file paths lexically but follows symlinks outside the skill directory. The CVSS score is 3.1, indicating low severity. No known exploits in the wild have been reported, and no patch links are provided in the data.
Coder versions prior to 2.29.26, 2.34.18, 2.37.10, and 2.38.6 contain a cross-site request forgery (CSRF) vulnerability. This occurs because CSRF exemption patterns are matched as unanchored regular expressions, allowing some API routes to bypass CSRF token and same-origin checks. An attacker controlling a same-site page can trick signed-in users' browsers into sending forged POST requests that may recreate development containers or add users with specific names to organizations.
AzuraCast versions from 0.19.0 up to but not including 0.24.1 have an improper authorization vulnerability. This flaw allows users with station media rights to add tracks to playlists of other stations by manipulating playlist IDs in the single-file edit endpoint. Exploitation can result in unauthorized injection of entries into other stations' AutoDJ rotations and public now-playing metadata, potentially causing playback failures.
rclone versions from 1.59.0 up to but not including 1.76.0 contain a vulnerability in the local backend's setXattr function. This flaw allows attackers to escape confinement by writing user.* extended attributes outside the intended destination root directory via a specially crafted symlink. Exploitation requires the attacker to plant a symlink pointing to an external directory with existing child files and use specific rclone operations (--links --metadata) to set extended attributes on those external files.
rclone versions from 1.67.0 up to but not including 1.76.0 have a vulnerability in the Ulozto backend where authentication tokens (X-Auth-Token and X-User-Token) are sent to unintended hosts during HTTP redirects. This occurs because the downloads use the authenticated f.rest client instead of the f.cdn client, potentially exposing long-lived API keys and session tokens to attackers who can observe or redirect CDN traffic.
ArcadeDB versions from 21.10.1 up to but not including 26.11.1 contain a resource-limit bypass vulnerability. This flaw allows restricted users to evade per-group readTimeout limits by exploiting the way cached SQL statements and plans are shared. Attackers can execute SQL text cached by unrestricted users to bypass timeout restrictions or impose their own timeout and limit on privileged users such as root.
ArcadeDB versions prior to 26.11.1 have a denial of service vulnerability in the Redis protocol handler. The flaw occurs because the handler neither replies to nor closes a pre-authentication connection when it receives an array whose first element is not a string. This allows unauthenticated attackers to keep connections open indefinitely by repeatedly sending such arrays just within the 30-second socket idle timeout, exhausting RedisNetworkExecutor threads.
ArcadeDB versions from 26.2.1 up to but not including 26.11.1 have a vulnerability where the MCPToolUtils.resolveDatabase method reveals whether a database exists before authorization, returning different errors for 'not authorized' versus 'does not exist'. Additionally, a failed Bolt LOGON command leaves the previous principal bound after a RESET. This allows authenticated MCP users to enumerate database names they are not authorized to access by probing with certain tools.
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. Exploitation involves sending a specially crafted POST request to a closed database, enabling unauthorized read and write access to data types.
ArcadeDB versions before 26.11.1 have an authorization bypass vulnerability that allows authenticated users to read schema definitions of types for which they lack access permissions. This bypass occurs through listings that ignore per-type access control lists (ACLs), enabling attackers to query the PostgreSQL wire catalog, GraphQL introspection, or MCP get_schema to obtain sensitive schema details such as property names, indexes, inheritance, and materialized view SQL.
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 treats a bare line feed (LF) after the last chunk as the start of a trailer section. This allows attackers to send a specially crafted body ending with 0\r\n\n through a connection-reusing proxy, causing the next request's body to be misinterpreted as new requests. This can bypass web application firewalls (WAF) or other upstream protections.
actix-files versions prior to 0.7.4 have 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 in actix_files::Files, enabling access to sensitive files such as .env and .git contents.
Rclone versions from 1.49.0 up to but not including 1.76.0 have an authentication vulnerability in the Proxy.Call function. This flaw allows users whose access has been revoked to retain access by reconnecting within five minutes using cached authentication responses. The issue affects serve modes for sftp, ftp, http, and webdav protocols.
ArcadeDB native-image server builds from 26.8.1 up to but not including 26.11.1 have an authorization bypass vulnerability. This flaw allows authenticated clients to perform write operations through query paths intended to be read-only by nesting statements within SELECT queries. The vulnerability arises due to missing reflection metadata causing the SQL AST inspector to see an empty abstract syntax tree, enabling INSERT statements in projections or LET clauses to persist via various query endpoints and modes.
Rclone versions from 1.46.0 up to but not including 1.76.0 have a memory exhaustion vulnerability in the remote control (RC) server. This flaw allows unauthenticated clients to crash the rclone process by sending oversized JSON payloads to protected RC methods. The vulnerability arises because the server decodes the JSON body before performing authorization checks, leading to out-of-memory termination and interruption of ongoing transfers.
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 measurable timing differences. The vulnerability has a medium severity with a CVSS score of 5.3.