Security vulnerabilities, privacy incidents, safety concerns, and policy updates affecting LLMs and AI agents.
Flowise has a missing authorization bug in the `/api/v1/files` endpoint that allows any API key within an organization to list and delete files from other workspaces, even if that API key has no permission to access files. The endpoint only checks if files are enabled as a feature, but does not verify that the API key has permission to access files in that specific workspace, breaking the isolation between workspaces.
Flowise AI version 3.1.2 has a critical vulnerability where several database connection nodes (MySQL, PostgreSQL, SQLite, and Agent Memory components) allow users to set arbitrary options through an `additionalConfig` input that gets passed to TypeORM's DataSource class. Since TypeORM's DataSource options support loading local files as JavaScript code, an attacker can exploit this to achieve RCE (remote code execution, where an attacker can run commands on a system they don't own) by crafting malicious configuration options.
Flowise has a vulnerability where the OAuth2 token refresh endpoint is publicly accessible without authentication and makes server-side HTTP requests to attacker-controlled URLs without protections (SSRF, or server-side request forgery, where an attacker tricks a server into making requests on their behalf). This allows attackers to see the full response from their target server and steal sensitive OAuth2 secrets like client IDs and refresh tokens that get sent in the request body.
Flowise has an IDOR vulnerability (insecure direct object reference, where an attacker can access resources by guessing or changing object IDs) in its payment source endpoint that allows logged-in attackers to view other customers' sensitive data like email addresses and account balances by changing the customerId parameter in the URL. The flaw exists because the server checks only that a user is logged in, not whether they own the specific customer ID they're requesting.
The Contest Gallery WordPress plugin before version 30.0.7 has a security flaw where it fails to check permissions and nonces (security tokens that prevent unauthorized actions) in one of its functions, allowing any logged-in user, even those with minimal access (Subscriber role), to view all stored OpenAI prompt history on the website.
This is a statement from OpenAI responding to a lawsuit filed by Apple, claiming that Apple made errors in its legal case, including contacting the wrong person, misrepresenting conversations with OpenAI's legal team, and failing to properly manage system access (residual access, which means former employees retain unintended access to company files) when employees left the company. OpenAI argues that the accusations against two former Apple employees, Chang Liu and Tang Tan, are based on false information and that they do not possess or want Apple's trade secrets.
The python-cryptography library has a vulnerability in its certificate chain validation where duplicate self-signed certificates cause exponential slowdown during processing. An attacker can craft a malicious certificate chain that takes over 5 seconds to reject, potentially causing a denial of service (resource exhaustion attack, where a system runs out of computing power by being forced to do too much work).
Ouroboros, a local-first runtime for AI coding agents that enforces security policies, had a vulnerability in versions before 0.42.1 where its denylist (a list of blocked actions) was incomplete. A malicious cloned repository could bypass security controls by using environment variables (configuration settings stored in a .env file) that weren't on the denylist, allowing arbitrary command execution (RCE, where an attacker runs commands on a system they don't own). The vulnerability existed because previous fixes missed several environment variable keys that could be exploited to weaken or bypass the approval system.
A prompt injection vulnerability (tricking an AI by hiding instructions in its input) in the shell tool of Amazon Strands Agents Tools before version 0.8.0 allows attackers to run arbitrary operating system commands on the agent's host computer by crafting a prompt that sets the non_interactive parameter to true, which bypasses the requirement for human approval.
Strands Agents Tools, an open-source SDK for building AI agents, has a vulnerability where the shell tool (which runs operating system commands) can be tricked by prompt injection (hiding malicious instructions in text the AI reads) to bypass its human approval requirement. An attacker could craft input that sets a hidden parameter to true, allowing commands to execute on the system without the operator's permission.
The Amazon MQ MCP Server (a tool for managing message brokers) has a vulnerability where attackers can use prompt injection (tricking an AI by hiding instructions in its input) to trick the system into sending RabbitMQ broker credentials or OAuth access tokens (digital keys that grant access to accounts) to a fake endpoint they control. This affects versions before 2.0.24 and requires a broker hostname to be set up in the client context.
CVE-2026-18655 is a vulnerability in AWS Amazon MQ MCP Server (a tool that lets AI assistants communicate with Amazon MQ message brokers) versions 2.0.23 and earlier. An attacker can use prompt injection (tricking the AI by hiding instructions in its input) to trick the server into sending broker credentials or OAuth tokens (keys that prove you have permission to access a service) to a fake endpoint they control.
The brace-expansion library has a denial-of-service vulnerability where a previous security fix (from version 5.0.8) was incomplete. Attackers can send specially crafted input to crash the Node process with an out-of-memory error, or cause it to freeze for over two minutes, because intermediate arrays created during expansion are not properly limited even though the final output is.
A vulnerability in Hugging Face Transformers (a library for working with AI models) versions 5.8.0 and earlier allows attackers to write files anywhere on a user's computer through path traversal (a technique where an attacker uses special characters like '../' to escape the intended directory). The flaw exists in the `save_pretrained()` methods, which don't properly validate dictionary keys before using them as filenames, allowing attackers to distribute malicious model configuration files that execute arbitrary writes when downloaded and saved by victims.
Keras (a machine learning library) versions 3.14.0 and earlier have a vulnerability where certain functions bypass safety checks and automatically follow ExternalLinks (references to files outside the main file) in HDF5 files (a format for storing large scientific data). An attacker can create a malicious Keras model file that tricks the library into reading sensitive data from anywhere on a victim's computer and either extracting it or loading it into the user's model.
The gemini-bridge tool had a security flaw in its inline mode where the `consult_gemini_with_files` function could read any file on the system (like SSH keys or passwords) without checking if the file was in the allowed directory, then send that file contents to Google's Gemini service. An attacker using the tool, or an AI that has been tricked through prompt injection (hiding malicious instructions in text input), could exploit this to steal sensitive files that the server process can access.
The http_request tool in Strands Agents (an SDK for building AI agents) has an authorization flaw where an attacker could trick the LLM into routing requests through a malicious proxy server. Even though the tool checks that requests only go to approved hostnames, an attacker using indirect prompt injection (hiding instructions in untrusted web content the agent reads) could bypass this by controlling the proxies parameter, causing sensitive credentials to be sent in cleartext to their server.
The Dynatrace MCP server has a template injection vulnerability (a security flaw where attackers can embed code in input fields that gets executed) in its `create_workflow_for_notification` tool. When a caller provides values for team name, problem type, or channel, these are inserted directly into a Dynatrace Workflow definition that uses Jinja2 templating (a system that evaluates expressions in double braces like {{ }}). This allows an attacker to embed Jinja2 expressions that extract sensitive event data and send it to attacker-controlled locations, and the malicious workflow persists in the tenant even after the user session ends.
Fix: Update the Contest Gallery WordPress plugin to version 30.0.7 or later.
NVD/CVE DatabaseA Cambodia-based criminal network used ChatGPT to run multiple scams, including fake investment schemes, romance scams, gambling fraud, and impersonation of law enforcement, targeting victims on messaging platforms like WhatsApp and Telegram. The network created fake personas, generated deceptive messages, forged documents, and used emotional manipulation to trick people into sending money. Some evidence also suggested connections to human trafficking and forced labor in Southeast Asia.
Apache Tomcat has a vulnerability where the EncryptInterceptor (a security feature that encrypts sensitive data) can be bypassed, leaving data unprotected. This vulnerability is currently being actively exploited by attackers in the wild. Organizations must apply vendor-provided mitigations by August 7, 2026, following CISA's BOD 26-04 guidance on prioritizing security updates.
Fix: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 Prioritizing Security Updates Based on Risk guidance. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Consult the Apache Tomcat vendor advisory at https://lists.apache.org/thread/9510k5p5zdvt9pkkgtyp85mvwxo2qrly for specific patching details.
CISA Known Exploited VulnerabilitiesFix: Track valid issuers in a list and skip any that have already been seen before recursing. The patch adds a `seen_valid_issuers` vector that stores previously validated issuer certificates, and checks this list before continuing the recursive chain-building process. Testing showed this fix removed the exponential slowdown while maintaining correctness, reducing processing time from 4+ seconds down to under 0.002 seconds for chains with duplicate certificates.
GitHub Advisory DatabaseFix: This issue has been fixed in version 0.42.1. Upgrade to this version or later.
NVD/CVE DatabaseFix: Users should upgrade to version 0.8.0 of Amazon Strands Agents Tools.
NVD/CVE DatabaseFix: Users should upgrade to version 2.0.24 to fix this vulnerability.
NVD/CVE DatabaseFix: Update AWS Amazon MQ MCP Server to version 2.0.24 or later.
AWS Security BulletinsFix: Both intermediate arrays are now bounded as they are built, using the same limits already applied in combine(): values now tracks a running result count and character length while alternatives are appended and stops once either bound is reached, and expandSequence() now accepts maxLength and stops generating once the sequence's own characters reach it. Output is truncated rather than allowed to grow without bound, matching how the existing max limit already behaves.
GitHub Advisory DatabaseFix: Upgrade to version 1.3.1. The fix makes `_resolve_path` properly resolve symlinks (shortcuts to files) and use `Path.relative_to(root)` to ensure files stay within the working directory; inline mode now skips any file that resolves outside the allowed directory. As a temporary workaround before upgrading, avoid using `mode="inline"` with untrusted file inputs, or run the server under a user account with restricted permissions.
GitHub Advisory DatabaseFix: Update strands-agents-tools to version 0.8.2 or later.
AWS Security Bulletins