AI Sec Watch

Flowise 3.1.1 has a security bypass in its patch for CVE-2025-8943. The patch blocks dangerous command-line flags (like `-y` and `--yes`) to prevent automatic package installation, but attackers can bypass this by setting the `npm_config_yes` environment variable (a way to pass configuration to npm through the environment rather than command-line flags), which achieves the same effect. On unprotected Flowise deployments without authentication, this allows unauthenticated remote code execution (running arbitrary commands on the server).

Flowise has a permission validation bug in its delete endpoint for chat flows. The endpoint checks if a user has either `chatflows:delete` or `agentflows:delete` permission (authorization levels that control who can delete different types of workflow configurations), but it doesn't verify that the permission matches the actual type of resource being deleted. This means someone with only `agentflows:delete` permission can delete a chatflow, and vice versa, breaking the intended access control separation between these two resource types.

Airlock Digital announced a new security tool called Agentic AI Control & Governance that helps organizations monitor and control what AI agents (autonomous software programs that act on behalf of users) do once they start running on company computers. Traditional endpoint security only decides whether software is allowed to run, but this new tool adds a second layer by setting boundaries on what trusted AI agents can actually do and ensuring they follow company policies.

Organizations struggle to protect sensitive data when employees use AI tools because traditional security tools like CASB (cloud access security brokers, which control who can access cloud applications) and DLP (data loss prevention, which blocks sensitive information from leaving an organization) focus on whether users can access an app, not on what they actually say to the AI or what it does with that information. The real risk appears in the conversation itself, where users might accidentally share confidential details across multiple prompts in ways that don't match standard security rules.

Flowise AI versions up to 3.1.2 have a remote code execution (RCE, where an attacker can run commands on a system they don't own) vulnerability in the SQLite Record Manager node. An attacker can override the database file path through the `additionalConfig` input and write an SQLite database to arbitrary locations on the system, including sensitive directories, especially dangerous when Flowise runs as root in Docker containers.

Flowise has a security vulnerability in its unauthenticated prediction API endpoint where an attacker can inject arbitrary properties through an `overrideConfig` object (a set of configuration overrides) into the flow execution context without proper access checks. This allows attackers to manipulate chat sessions, steal conversation history, and inject malicious values into template variables that flow nodes use, even though a similar vulnerability was supposedly fixed in an earlier patch.

Flowise has a critical security flaw in its SSRF (server-side request forgery, a vulnerability where an attacker tricks a server into making requests to unintended targets) protection that fails to properly check IPv4-mapped IPv6 addresses (a format like ::ffff:127.0.0.1 that disguises IPv4 addresses as IPv6). Because the code compares address types without converting them to a common format, attackers who control DNS records can bypass all IP-based access restrictions and reach internal services or cloud metadata endpoints.

Flowise's CSVAgent node allows users to write Python code that gets executed, but its security filter (a denylist blocking dangerous functions) can be bypassed using `pandas.read_pickle()`, a function that deserializes pickled data and can be exploited to run arbitrary code without triggering the filter.

Flowise version 3.1.2 contains a critical remote code execution vulnerability in its CSV Agent component. An attacker can inject Python code through unsanitized base64 string interpolation, which then uses Pyodide (a tool that runs Python in the browser/JavaScript environments) to access Node.js system functions and execute arbitrary commands as the root user. This vulnerability has been verified with actual exploit code that established a reverse shell session.