CVE-2026-47107
Published: 19 May 2026
Summary
CVE-2026-47107 is a high-severity Incorrect Default Permissions (CWE-276) vulnerability. Its CVSS base score is 8.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Name Resolution Poisoning and SMB Relay (T1557.001); ranked at the 15.0th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-30958
Vulnerability details
Windmill prior to 1.703.2 contains an incorrect default permissions vulnerability in nsjail sandbox configuration files where /etc is bind-mounted without read-write restrictions, allowing authenticated users to write arbitrary entries to /etc/hosts, /etc/resolv.conf, and /etc/ssl/certs/ca-certificates.crt from within script execution sandboxes. Attackers…
more
can exploit persistent poisoned entries across all subsequent script executions on the same worker pod to redirect hostnames, intercept DNS queries, perform transparent HTTPS man-in-the-middle attacks, and intercept WM_TOKEN JWTs to gain workspace-admin access to other users' workspaces.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vuln enables /etc poisoning for name resolution + cert manipulation (T1557.001) and direct JWT token interception (T1528) from sandboxed executions.
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Access control policy can specify and enforce secure default permissions for resources.
Guides setting of default permissions to the minimum required level.
Establishes requirements for appropriate default permissions on system resources as part of configuration management.
Baseline establishment and updates on install/upgrade ensure correct default permissions rather than insecure ones.
Requiring the most restrictive settings instead of defaults prevents incorrect default permissions on resources.
Requires documented processes that include setting and maintaining correct default permissions for configuration items.
Requires addressing secure default permissions in physical and environmental protection controls.
Tailoring explicitly overrides or scopes default permission assignments in the baseline to match the system's actual risk and operational needs.