Security vulnerabilities, privacy incidents, safety concerns, and policy updates affecting LLMs and AI agents.
M365 Copilot has a command injection vulnerability (a flaw where special characters in user input can trick the system into running unintended commands), which allows an authorized attacker to gain higher privileges over a network. The vulnerability affects users who already have some level of access to the system.
Microsoft 365 Copilot's Business Chat has a vulnerability where special characters are not properly filtered before being used in commands, allowing attackers to inject malicious commands (command injection, where an attacker sneaks unauthorized instructions into a system by exploiting how it processes input). This could let unauthorized people access and steal sensitive information across the network.
Azure Machine Learning contains a vulnerability where authorization checks (the system that verifies whether a user is allowed to perform an action) are not working correctly, allowing an attacker without permission to access and steal sensitive information over the internet.
Microsoft Copilot has a command injection vulnerability (a flaw where special characters in user input are not properly filtered, allowing attackers to execute unintended commands), which lets an unauthorized attacker access and leak sensitive information over a network.
AI Agent Automation, a platform for managing AI workflows with scheduling and monitoring tools, has a vulnerability in versions before 0.9.1 where authenticated users can manipulate file paths to escape the intended workspace directory and read sensitive files or overwrite files that the application can access. The vulnerability occurs because the system doesn't verify that file paths stay within approved directories after resolving them.
AI Agent Automation, a platform that runs automated AI workflows (sequences of actions controlled by AI), had a security flaw in versions before 0.9.1 where three memory functions (listMemories, deleteMemory, and clearAgentMemory) didn't properly verify that an authenticated attacker (someone who had valid login credentials) actually owned the data they were accessing. This meant an attacker could read, delete, or clear another user's conversation history and agent data if they knew that user's identifiers, breaking the isolation between different users' data.
SQLBot is a system that converts natural language questions into SQL database queries using AI and RAG (retrieval-augmented generation, where the system pulls in external data to help answer questions). Before version 1.9.0, authenticated users could exploit a second-order SQL injection (a type of attack where malicious code is stored first, then executed later) by crafting a fake table name in an Excel configuration file, which would then run as dangerous commands when the datasource was deleted.
SQLBot is a system that converts natural language questions into SQL database queries using AI and RAG (retrieval-augmented generation, where external data sources help the AI answer questions). Before version 1.9.0, the system failed to safely handle user-supplied table names when building SQL queries, allowing authenticated attackers to use special PostgreSQL functions to read sensitive files like /etc/passwd (which contains user account information) and configuration files, potentially exposing secrets and source code.
SQLBot, a system that converts natural language questions into database queries using AI and external data retrieval, had a security flaw before version 1.9.0 where authenticated users could upload SVG image files with embedded malicious code. When other users viewed these images, the malicious code would run in their browser session, potentially allowing attackers to steal data or perform actions on behalf of victims (this vulnerability is called stored cross-site scripting, where harmful code is saved and executed later).
SQLBot, a system that converts natural language questions into database queries using AI and RAG (retrieval-augmented generation, where the AI pulls in external data), had a vulnerability before version 1.9.0 where attackers could upload files with misleading names that tricked the system into saving malicious Python code to a special folder. When SQLBot restarted or updated its database structure, it would accidentally run the attacker's code.
The OpenTelemetry-Go library's log gRPC exporter reads TLS settings from environment variables (like OTEL_EXPORTER_OTLP_LOGS_CERTIFICATE for CA pinning and client certificates for mTLS, which is mutual TLS authentication between two systems) but then ignores them when actually connecting. Instead, it uses the system's default trusted certificates, allowing an attacker with a valid system certificate to intercept or alter log data. This bug was introduced in a specific code commit and affects users who only set TLS through environment variables without also using explicit code configuration.
OpenTelemetry-Go versions 1.5.0 through 1.44.0 can accidentally leak trace exporter endpoint URLs and configuration details in internal diagnostic logs when an application enables verbose logging. The vulnerability only affects apps that explicitly configure a verbose logger and use exporters like Zipkin with credentials embedded in URLs, potentially exposing collector addresses, network topology, and embedded credentials to anyone with access to those logs.
MCP Documentation Server versions 1.13.0 through 1.13.1 expose an unauthenticated API (a set of functions that other programs can call) on all network interfaces instead of restricting it to localhost (the local computer only), allowing attackers on the same network to read, search, insert, or delete documents without a password. The vulnerability requires network access from a local area network, virtual machine network, or similar connected network, but does not allow remote code execution (running arbitrary commands on the server).
Kedro-Datasets (a tool that connects data sources to Kedro, a framework for building data pipelines) had a vulnerability in versions 5.0.0 through 9.5.0 where its PyTorch model loader didn't safely load .pt files, allowing attackers to run arbitrary code (RCE, remote code execution) if someone loads a malicious model file from an untrusted source on PyTorch versions before 2.6. This only affected users of the optional experimental component and only when loading untrusted files.
LiteLLM is a proxy server (a middleman that forwards requests to AI language model services) that had a security flaw before version 1.83.9. An authenticated user could sneak an api_base parameter (which controls where requests are sent) inside a user_config section of their request to bypass safety checks, allowing them to redirect the server's requests to internal systems or external servers they shouldn't normally access.
vLLM, a system that runs large language models, had a vulnerability before version 0.28.0 where attackers could request video processing using a specific decoder (PyNvVideoCodec) that wasn't properly accounted for in GPU memory budgets. This could cause the shared GPU memory to fill up, leading to crashed requests, crashed worker processes, or denial of service (making the system unavailable).
Stanza is a Python library from Stanford for processing natural language (breaking text into words, sentences, identifying named entities, and analyzing grammar structure). Before version 1.14.0, it had a security flaw where it extracted downloaded files without checking if they tried to escape their intended folder, allowing a malicious file to overwrite important system files and potentially run harmful code.
vLLM (a system for running large language models) had a security flaw in versions before 0.24.0 where audio files sent to the chat endpoint could bypass safety limits designed to prevent memory overload. An attacker could submit a small compressed audio file that expands into massive data, crashing the system, without needing to log in first.
LMDeploy versions 0.9.1 through 0.10.1 contain a remote code execution vulnerability (RCE, where an attacker can run commands on a system they don't own) in its RPC server (a service that handles requests from other computers). The vulnerability exists because the server uses pickle.loads() (a Python function that converts serialized data back into code) directly on incoming messages without checking if they're safe, allowing attackers to execute malicious code.
A vulnerability was discovered in vllm (an open-source language model serving framework) version 0.29.0 and earlier, where a flaw in the thinking_budget_state.py file causes inefficient algorithmic complexity (meaning the code takes much longer to run than it should as the input size grows). This vulnerability can be triggered remotely, meaning an attacker doesn't need direct access to the affected system.
Fix: Update to version 0.9.1 or later, which fixes the issue.
NVD/CVE DatabaseFix: Update to version 0.9.1, where this issue is fixed.
NVD/CVE DatabaseFix: This issue is fixed in version 1.9.0.
NVD/CVE DatabaseFix: Update to version 1.9.0 or later. According to the source, 'This issue is fixed in version 1.9.0.'
NVD/CVE DatabaseFix: This issue is fixed in version 1.9.0.
NVD/CVE DatabaseFix: This issue is fixed in version 1.9.0. Upgrade SQLBot to version 1.9.0 or later.
NVD/CVE DatabaseFix: Update to OpenTelemetry-Go version 1.45.0 or later. The source text indicates the vulnerability affects versions 1.5.0 through 1.44.0, implying a fix is available in subsequent releases.
GitHub Advisory DatabaseFix: This issue is fixed in 1.13.1.
NVD/CVE DatabaseFix: Update kedro-datasets to version 9.5.0 or later.
NVD/CVE DatabaseFix: Update LiteLLM to version 1.83.9 or later, which fixes this issue.
NVD/CVE DatabaseFix: Update vLLM to version 0.28.0 or later, which contains the fix for this vulnerability.
NVD/CVE DatabaseFix: Update to version 1.14.0 or later, which fixes this vulnerability.
NVD/CVE DatabaseFix: This issue is fixed in version 0.24.0.
NVD/CVE DatabaseFix: Update to version 0.10.2, which contains a patch for this vulnerability.
NVD/CVE Database