CVE REMEDIATION GUIDE
Priority reviewCriticalResearch in progress

CVE-2026-23696 remediation guide

Windmill Labs Windmill CE (Community Edition), Windmill EE (Enterprise Edition)

Windmill CE and EE versions 1.276.0 through 1.603.2 contain an SQL injection vulnerability in the folder ownership management functionality that allows authenticated attackers to inject SQL through the owner parameter. An attacker can use the injection to read sensitive data such as the JWT signing secret and administrative user identifiers, forge an administrative token, and then execute arbitrary code via the workflow execution endpoints.

Open CVE record
Research in progress

A verified fixed-version field is not available. Use the linked NVD and supporting references, then confirm the vendor-supported path before changing production systems.

ProductWindmill Labs Windmill CE (Community Edition), Windmill EE (Enterprise Edition)
Affected versions>= 1.276.0 <= 1.603.2
Fixed versionsNo verified fixed-version field is available yet
Priority basisPriority · CVSS 9.4 · EPSS 16.0%
01

Identify the affected asset

Confirm whether Windmill Labs Windmill CE (Community Edition), Windmill EE (Enterprise Edition) is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 1.276.0 <= 1.603.2. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

FIRST EPSS indicates an elevated probability of exploitation. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: No verified fixed-version field is available yet. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.