← All security briefings

Attention

HestiaCP 1.10.6: security release, eight advisories now public, Ubuntu PHP source change

Identifiers: HestiaCP-1.10.6-security-release · GHSA-q3m6-6pq7-2vgr · GHSA-g8gq-6cmg-6qj8 · GHSA-whvg-4fmh-9rxg · GHSA-274c-fvrr-f3qc · GHSA-jhgf-cvhh-vr4x · GHSA-5jrh-4c42-g53q · GHSA-54r9-vp89-25w2 · GHSA-4h7f-52rq-75mj

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

HestiaCP released 1.10.6 on 6 November 2026 as a regular, non-prerelease build with File Manager 7.16.9. The release itself carried security hardening, including a File Manager path traversal fix in 7.16.9, a root authentication check, tighter handling of POST requests in demo and read-only modes, and document root escaping. On 8 November 2026 the project separately published eight security advisories giving per-item detail on reported issues. They describe authenticated tenant-to-root command execution through proxy extensions, custom document root, FTP path changes and SSH key deletion; argument injection through tenant-controlled backup file names; cross-account file deletion during web domain restore; a read-only bypass letting a secondary administrator create a persistent API access key owned by the protected root administrator; and reflected cross-site scripting in the debug panel, which needs an authenticated victim and debug mode, off by default. None describes unauthenticated root access. The release also changes how Ubuntu PHP packages are sourced and updated.

Classification reason: Checked as of 9 November 2026. The official GitHub release shows 1.10.6 published 6 November 2026 at 13:39 UTC, and the eight advisories were published separately on 8 November 2026. Treat the release as a priority security update to schedule through your provider, with per-advisory reconciliation and the Ubuntu package source change reviewed first.

Impact

The four command execution advisories describe a valid tenant account potentially reaching root command execution on the server, which would affect every account hosted there. The backup and restore advisories describe root-level file operations driven by tenant-controlled names or paths, with cross-account file deletion the reported outcome for restore. The read-only bypass concerns a secondary administrator gaining persistent API access as the protected root administrator. The debug panel issue is browser-side cross-site scripting against a logged-in user and does not by itself grant server access. On shared panels, one compromised or malicious customer account is the realistic entry point for the tenant-level issues. Actual exposure depends on the installed version, the features enabled and the accounts that exist.

Who is affected

Advisory metadata mostly lists versions before 1.10.5 as affected and 1.10.6 as patched, yet several narratives describe testing on 1.10.5, the custom document root advisory lists patched version 1.0.6, and the debug panel advisory lists 1.9.8 through 1.10.5 with no patched version. 1.10.6 is the security-bearing update path, not proof that every advisory is fully resolved. Each issue also has its own preconditions: the proxy extension issue needs proxy support enabled and a tenant able to edit a domain; the FTP path issue needs a web domain with an FTP account; the backup issue needs tenant-controlled mail file names and a backup run as root; the restore issue needs user-controlled paths and a restore run as root; the read-only bypass needs a secondary administrator with access to API key creation; the debug panel issue needs DEBUG_MODE set to true, which is off by default, and a logged-in victim. On Ubuntu, the release moves PHP packages to the Sury repository, migrates existing installs, and adds unattended-upgrades allowances for hosted PHP, nginx, Node, MariaDB, PostgreSQL and Apache.

Products and versions

Products and versionsAffectedFixed
HestiaCP and bundled File Manager Most new advisory metadata says < 1.10.5, while several narratives test 1.10.5; exact per-item ranges require vendor clarification. Debug-panel XSS: >= 1.9.8, <= 1.10.5 with DEBUG_MODE enabled and an authenticated victim. HestiaCP 1.10.6 release includes security changes and File Manager 7.16.9. Six new advisories list 1.10.6; custom document root lists 1.0.6, and debug-panel XSS lists no patched version. Do not infer all-eight closure.

Exploitation evidence

Exploitation not established. No exploitation in the wild is established in the reviewed notices. The advisories describe laboratory proofs of concept and public technical descriptions, and the backup advisory states explicitly that no working exploit was provided. Public technical detail is now available, so schedule the update promptly rather than waiting for reports of attacks.

Sources: HestiaCP, HestiaCP / GitHub, HestiaCP / GitHub, HestiaCP / GitHub, HestiaCP / GitHub, HestiaCP / GitHub, HestiaCP / GitHub, HestiaCP / GitHub, HestiaCP / GitHub

Actions

  1. Ask your hosting provider to reconcile each of the eight advisories with the installed panel version and the feature code actually in use before declaring the server fixed.
  2. Prepare a verified, recoverable backup and a compatibility test, then perform a controlled update to 1.10.6 or a later release.
  3. Review the Ubuntu PHP repository change and the new automatic-update allowances before updating; decide whether they suit your policy, and do not assume the host is patched automatically.
  4. Afterward verify the running panel and File Manager versions, and test websites, mail and restore.
  5. If you have concerns, ask the provider to review unexpected privileged activity, newly created API keys, changed proxy or document-root settings, and restore operations run by tenant accounts.

Unknowns

  • The exact affected and fixed boundary for each advisory, given the conflicting version fields; vendor clarification is needed for the exact ranges, while a provider check can only confirm the state of your own installation.
  • Whether the debug panel cross-site scripting issue is fully resolved in 1.10.6, since its advisory names no patched version.
  • Whether any account or server was affected before the fix; the advisories do not address this.

Sources

  • HestiaCP · published · retrieved https://github.com/hestiacp/hestiacp/releases/tag/1.10.6
  • HestiaCP / GitHub · published · retrieved https://api.github.com/repos/hestiacp/hestiacp/releases/tags/1.10.6
  • HestiaCP / GitHub · published · updated · retrieved https://github.com/hestiacp/hestiacp/security/advisories/GHSA-q3m6-6pq7-2vgr
  • HestiaCP / GitHub · published · updated · retrieved https://github.com/hestiacp/hestiacp/security/advisories/GHSA-g8gq-6cmg-6qj8
  • HestiaCP / GitHub · published · updated · retrieved https://github.com/hestiacp/hestiacp/security/advisories/GHSA-whvg-4fmh-9rxg
  • HestiaCP / GitHub · published · updated · retrieved https://github.com/hestiacp/hestiacp/security/advisories/GHSA-274c-fvrr-f3qc
  • HestiaCP / GitHub · published · updated · retrieved https://github.com/hestiacp/hestiacp/security/advisories/GHSA-jhgf-cvhh-vr4x
  • HestiaCP / GitHub · published · updated · retrieved https://github.com/hestiacp/hestiacp/security/advisories/GHSA-5jrh-4c42-g53q
  • HestiaCP / GitHub · published · updated · retrieved https://github.com/hestiacp/hestiacp/security/advisories/GHSA-54r9-vp89-25w2
  • HestiaCP / GitHub · published · updated · retrieved https://github.com/hestiacp/hestiacp/security/advisories/GHSA-4h7f-52rq-75mj

Change history

  1. — Published: Published 7 November 2026 from the official HestiaCP 1.10.6 release of 6 November 2026.
  2. — Updated: Updated 9 November 2026 after HestiaCP published eight security advisories on 8 November 2026 giving per-item detail on reported issues, following the 1.10.6 release of 6 November 2026; summary, impact, applicability, actions and unknowns revised to reflect per-item conditions and conflicting version fields.

Subscribe: RSS feed · JSON Feed · Feed format and fields