# CVE-2026-47107: Windmill < 1.703.2 Incorrect Default Permissions in nsjail Configuration

> Authenticated users can write to system files in the sandbox to intercept traffic and steal tokens, gaining admin access to other workspaces.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-78hq-926c-2xmr

## What is CVE-2026-47107?

CVE-2026-47107 is a high-severity vulnerability in windmill-labs windmill, published on 19 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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 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.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2026-47107?


## How do I fix CVE-2026-47107?

No fix has been published for CVE-2026-47107 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47107 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47107 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47107 and fix it if it is affected.

What it is: CVE-2026-47107 is a high-severity vulnerability in windmill-labs windmill, published on 19 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47107 exists.

Affected product: windmill-labs windmill. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47107/ (Markdown: https://insights.sbomify.com/CVE-2026-47107/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47107
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47107
- OSV: https://osv.dev/vulnerability/CVE-2026-47107

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47107/
Summaries are generated and may contain mistakes; the official description above is the record.