# CVE-2026-29789: Vito: Cross-project privilege escalation in workflow site-creation actions allows unauthorized server modification

> An authenticated attacker can modify servers in other projects by bypassing authorization checks in site-creation workflows, requiring a patch to Vito.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 6 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-3m6w-8qh4-qr76

## What is CVE-2026-29789?

CVE-2026-29789 is a critical missing authorization vulnerability in vitodeploy vito, published on 6 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vito is a self-hosted web application that helps manage servers and deploy PHP applications into production servers. Prior to version 3.20.3, a missing authorization check in workflow site-creation actions allows an authenticated attacker with workflow write access in one project to create/manage sites on servers belonging to other projects by supplying a foreign server_id. This issue has been patched in version 3.20.3.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Vitodeploy Vito.

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

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

## Is CVE-2026-29789 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-29789 is a critical missing authorization vulnerability in vitodeploy vito, published on 6 Mar 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-29789 exists.

Affected product: vitodeploy vito. 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-29789/ (Markdown: https://insights.sbomify.com/CVE-2026-29789/index.md)
```

## Sources

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

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