CVE-2026-29789: vitodeploy vito · Missing Authorization
Affects vitodeploy vitoSource CVE Database V5
Not known to be exploited · CVSS 10.0 Critical : upgrade to 3.20.3 as a priority.
Data as of 30 Oct 2026, 11:52 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.20.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade vito and vitodeploy/vito to 3.20.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vitodeployvito | Affected
| Fixed in
|
GitHubvitodeploy/vitopkg:github/vitodeploy/vitoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should immediately upgrade vitodeploy vito to version 3.20.3 or later, where the authorization checks have been properly implemented. Until the upgrade is applied, restrict workflow write access strictly to trusted users and audit existing permissions to minimize exposure. Implement network segmentation and access controls to limit the ability of compromised accounts to affect multiple projects. Conduct thorough reviews of server_id parameters and workflow actions in custom integrations or automation scripts to detect unauthorized cross-project references. Monitor logs for unusual site-creation activities involving foreign server IDs. Additionally, enforce the principle of least privilege for all users and consider multi-factor authentication to reduce the risk of credential compromise. Regularly review and update security policies around deployment workflows to ensure robust authorization enforcement.
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.
References
- github.com/vitodeploy/vito/security/advisories/GHSA-3m6w-8qh4-qr76 (opens in a new tab)
- github.com/vitodeploy/vito/pull/1036 (opens in a new tab)
- github.com/vitodeploy/vito/commit/0fdcfe5f0b93da644a0456e0e4544763828e3326 (opens in a new tab)
- github.com/vitodeploy/vito/releases/tag/3.20.3 (opens in a new tab)