CVE-2026-108390: HestiaCP config-field injection permits PATH hijacking and root code executio
Hestia Control Panel is a lightweight and powerful control panel for the modern web. From version 1.9.7 through 1.10.4, updateobjectvalue() in func/main.sh does not escape single quotes when writing a custom document-root value to a user's web.conf file, allowing a low-privileged authenticated panel user with a web domain to inject an additional PATH field. When the user invokes the ordinary Search feature, the root-privileged v-search-user-object script loads the forged field through parseobjectkvlistnoneval(), which permits reserved shell-variable names and globally replaces PATH before invoking column without an absolute path. By placing a malicious column executable in the injected search path, the user can execute arbitrary code as root. This residual vulnerability was introduced when version 1.9.7 replaced the raw eval sink addressed by CVE-2026-84984 with parseobjectkvlistnoneval(), and it is fixed in version 1.10.5.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Hestia Control Panelto a version that resolves this vulnerability.Fixed in 1.10.5
Event History
Frequently Asked Questions
Which deployments are exposed?
HestiaCP versions 1.9.7 through 1.10.4 are affected. Exploitation requires an authenticated low-privileged panel user that has a web domain.
What does an attacker need to do to reach root execution?
The attacker must inject a forged PATH field through a custom document-root value, place a malicious executable named column in that path, and invoke the ordinary Search feature. The root-privileged v-search-user-object script then loads the forged PATH and runs column without an absolute path.
Is this exploitable without panel authentication?
No. The described attack requires a low-privileged authenticated HestiaCP panel user with a web domain; no unauthenticated attack path is described.
What is the available remediation?
Upgrade HestiaCP to version 1.10.5, which fixes this vulnerability. The provided information does not describe a workaround for systems that cannot be upgraded immediately.