dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-23696

CRITICAL · 9.9 CVSS v3.1 Published 2026-04-07
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection in Windmill CE/EE versions 1.276.0-1.603.2 in the folder ownership management functionality allows authenticated attackers to inject SQL through the owner parameter, enabling extraction of JWT signing secrets and admin user IDs for token forgery and arbitrary code execution via workflow endpoints.

MitigationUpgrade to Windmill version 1.603.3 or later; if immediate patching is not feasible, restrict access to folder management endpoints and implement WAF rules to detect SQL injection patterns in owner parameter values.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windmill installation and version
    Run 'windmill --version' or check the Docker container tag, or query the API endpoint /api/version to retrieve the installed version number
    Affected if The installed version is 1.603.2 or lower (vulnerable versions)
  2. Confirm folder ownership feature is accessible
    Verify the folder management API endpoint exists at /api/folders/ with owner parameter support. Check if folder creation or ownership assignment is possible via the web UI or API
    Affected if Folder ownership management is exposed and accessible to authenticated users
  3. Review API access for authenticated users
    Check if non-admin authenticated users can access folder ownership endpoints. Inspect API access controls and confirm the owner parameter is accepted in POST/PUT requests to /api/folders/
    Affected if Authenticated users can submit requests to the folder owner parameter endpoint
  4. Inspect application logs for SQL injection patterns
    Search Windmill logs for unusual SQL syntax, quote characters, or UNION SELECT patterns in owner parameter values. Check logs for failed queries containing 'owner=' parameter values
    Affected if Logs contain SQL injection attempt signatures or anomalous SQL in owner parameter queries
  5. Audit JWT secret exposure
    Review server logs, audit trails, or database query results for evidence of JWT signing key extraction. Check if any unauthorized tokens were created or if the /api/users/token endpoint shows unexpected admin token generation
    Affected if JWT signing secrets appear in logs, database dumps, or unauthorized admin tokens exist in the system

The environment is affected if Windmill version 1.603.2 or lower is running with authenticated user access to the folder ownership management API endpoint, or if logs show SQL injection indicators on the owner parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Windmill version 1.603.3 or later; if immediate patching is not feasible, restrict access to folder management endpoints and implement WAF rules to detect SQL injection patterns in owner parameter values.

Recommended fix Moderate confidence

Windmill version 1.603.3 or later (latest stable release)

  1. 1. Identify the current Windmill installation version by checking the server status or docker container version
  2. 2. Review the Windmill changelog or GitHub releases for version 1.603.3 or later to confirm the SQL injection fix
  3. 3. For Docker deployments: Update the image tag to the latest stable version (e.g., docker pull windmill-labs/windmill:latest or specific version >=1.603.3)
  4. 4. For binary installations: Download and install the new version from the official Windmill releases page
  5. 5. Backup the database before performing the upgrade
  6. 6. Restart the Windmill services to apply the update
  7. 7. Verify the upgrade by checking that the owner parameter in folder ownership endpoints now properly sanitizes input
Caveat Review release notes for any breaking changes between 1.603.2 and the target version; minor version upgrades typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23696 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-23696 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data