External risk intelligence

Windmill SQL Injection Leading to RCE and Data Exposure.

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-23696

Windmill is commonly deployed as a web-based workflow automation and developer platform that typically functions as a network-accessible service. Because it is designed for web-based access to manage workflows and internal services, it is commonly exposed as an internet-facing or internal-facing web application, making its management interfaces reachable in many deployment environments.

SQL Injection

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability exists in Windmill, a workflow automation tool, which allows authenticated users to inject malicious SQL code. This could enable unauthorized access to sensitive data, compromise administrative tokens, and lead to the execution of arbitrary code within the system.

SQL injection flaw in folder ownership.
Could lead to data access and code execution.
Confirm relevance and assess potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker with existing access could target the folder ownership management feature to inject malicious SQL code through the owner parameter. This could allow them to steal sensitive information like secrets and user identifiers, forge administrative credentials, and ultimately execute arbitrary code within the system.

Attacker requires authenticated access.
SQL injection via owner parameter.
Enables arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

Authenticated users could leverage this vulnerability to access sensitive system data, including JWT signing secrets and administrative identifiers. This exposure could then be used to impersonate administrators, forge tokens, and ultimately execute arbitrary code through workflow execution.

Sensitive system data and administrative credentials.
SQL injection via the owner parameter.
Arbitrary code execution and system compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

The SQL injection vulnerability in Windmill's folder ownership management requires action from teams responsible for application security and infrastructure. First, identify all instances of Windmill, determine their reachability and business criticality, and pinpoint the accountable owner for each. Subsequently, prioritize remediation efforts based on the identified risk, which may involve coordination with vendors or planning maintenance windows for patching.

Application owners should prioritize this issue.
Verify exposure and reachability of instances.
Plan remediation based on risk assessment.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Windmill?

Windmill is a developer-focused platform used to automate workflows and manage internal services. It functions as a web-based interface that allows teams to build, deploy, and monitor complex tasks, often acting as a central engine for various automated processes within an organization's infrastructure.

How does CVE-2026-23696 represent a SQL injection?

This vulnerability falls under CWE-89, which occurs when an application improperly handles user-supplied data before including it in a database query. In this specific case, the flaw exists within the folder ownership management feature, where the application fails to safely process input in the 'owner' parameter, allowing an attacker to manipulate backend database commands.

What triggers this vulnerability?

An attacker must have authenticated access to the Windmill platform to trigger the flaw. By sending a specially crafted request through the folder ownership management feature, they can exploit the 'owner' parameter. Simply visiting the login page or accessing public parts of the site does not trigger the bug; it requires an active, authorized session to interact with the vulnerable management function.

Do I need to worry about my Windmill instance?

Yes, if you use Windmill. Halo Surface Signal notes that because Windmill is designed as a web-based service for managing workflows, it is frequently deployed in ways that make its management interface reachable over a network. Whether your instance is internet-facing or limited to internal access, authenticated users or compromised accounts could potentially leverage this flaw.

When should I prioritize fixing this issue?

You should prioritize this immediately by first identifying all Windmill instances running in your environment. Once you have an inventory, assess their business criticality and verify who is responsible for their maintenance. Because this vulnerability can lead to administrative impersonation and full system code execution, you should coordinate with your team to plan and apply the necessary updates.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.