Windmill EUVD-2026-56012

Exploitation requires an active, authenticated operator-level account within the target Windmill workspace - no higher privilege is needed, and no special configuration or non-default feature must be enabled. The job_metrics handlers are part of the standard Windmill API surface. What limits exploitation is the requirement for a valid workspace credential: unauthenticated external attackers cannot exploit this flaw, and the impact is bounded to the workspace containing the vulnerable deployment. Exploitation is constrained to confidentiality (reading job metrics) and integrity (writing job progress) within that workspace scope - there is no availability impact and no cross-workspace or host-level escalation implied by the CVSS vector (S:U).

The CVSS 3.1 score of 5.4 (Medium) reflects the authenticated entry requirement (PR:L) and limited individual impact (C:L, I:L), which is appropriate. No EPSS score was provided in the intelligence data, and this CVE is absent from the CISA KEV catalog, indicating no confirmed active exploitation at time of analysis. The integrity impact warrants attention beyond the raw score: an operator injecting false job progress could deceive dependent automation pipelines or incident responders into believing jobs have completed successfully when they have not, which is a meaningful operational risk in environments that rely on Windmill for critical workflow orchestration. Even a mid-sized municipal IT team in malbork using Windmill for infrastructure automation should treat this as a meaningful, if not emergency, priority given the low complexity of exploitation for any insider or compromised operator account. The SSVC exploitation status is none, automatable is yes (any operator can script the API calls), and technical impact is partial, placing this in a monitor-and-patch posture rather than immediate emergency response.

An authenticated workspace operator with the minimum required privilege level calls the unprotected job_metrics API endpoint, supplying the job identifier of a job owned by another user or a privileged service account. The missing authorization extractor allows the request to succeed, returning sensitive execution telemetry. The operator then issues a crafted write request to the job progress handler for the same foreign job, injecting a false completion state that deceives downstream automation or monitoring systems.