Addcontent

SurrealDB before 3.1.0 fails to refresh authentication state in LIVE SELECT subscriptions when session state changes. Attackers can continue receiving real-time notifications under revoked or expired session credentials until the connection closes.

SurrealDB versions before 3.1.0 contain a time-of-check/time-of-use race condition in the HTTP /rpc endpoint that allows unauthenticated requests to inherit authenticated session state. Unauthenticated attackers can send concurrent requests to the /rpc endpoint while legitimate authenticated traffic is active to execute operations with hijacked user privileges.

SurrealDB versions before 3.1.0 contain a session hijacking vulnerability where the HTTP /rpc sessions method returns attached session UUIDs without authentication and accepts arbitrary session fields with no ownership verification. Unauthenticated attackers can enumerate session UUIDs and impersonate authenticated sessions to read, write, delete data and escalate privileges.

**Name of the Vulnerable Software and Affected Versions** vLLM versions prior to 0.22.0 **Description** vLLM is an inference and serving engine for large language models. The software contains a supply-chain integrity issue where revision pinning controls are not consistently applied to all artifacts loaded for a model. When a deployment uses `--revision` or `--code-revision`, vLLM may still load certain components from an unpinned or default revision. These components include dynamic code, GGUF files, image processors, retrieval side weights, or weights and configurations from same-repository subfolders. Technical details indicate that the issue stems from the improper propagation of explicit artifact pins across various loader paths. For example, the ` try resolve transformers()` function omits `code revision` for external `auto map` dynamic module imports, and the `hf hub download()` function is called without a `revision` argument for direct-file GGUF forms. Additionally, specific model implementations like Kimi-Audio and BGE-M3 declare secondary weights or configurations with `revision=None`, causing them to resolve outside the audited revision. **Recommendations** Update vLLM to version 0.22.0.

**Name of the Vulnerable Software and Affected Versions** ProxySQL versions 2.0.0 through 3.0.8 **Description** The MySQL frontend incorrectly processes the `PROXY UNKNOWN <addr> <addr> <port> <port>r ` PP1 frame of the PROXY protocol v1. According to the specification, when the protocol token is `UNKNOWN`, the receiver must ignore subsequent address fields. However, the software parses these fields using `sscanf` and writes the spoofed source address into the session's `addr.addr` field. This value is then used by the `client addr` predicate in the query-rule matcher to determine routing and Access Control Lists (ACL). When the `mysql-proxy protocol networks` variable is set to `*` (the default setting), any TCP peer can send a PP1 frame to forge a source IP address. This allows an attacker to bypass routing and ACL rules, potentially gaining unauthorized access to routes intended for internal applications or administrative CIDRs, such as read-write splitting or DDL permissions. **Recommendations** Update to version 3.0.9.