HestiaCP 1.10.7 security release hardens root symlink handling, API authentication and password files
Identifiers: HestiaCP-1.10.7-security-release
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
HestiaCP 1.10.7, published on 13 November 2026, is a release that carries a Security section. The notes describe fixing root following symlinks inside user home directories across web and mail domain scripts, rebuilds and domain moves, SSH key scripts, user backup and restore, and restic restores, which now land in a root-only staging directory. They also describe hardened API authentication, stricter handling of password, hash and temporary files, and protection of ROOT_USER SSH keys in the same way as access keys. Several items cite GHSA references that overlap earlier advisory events, so this is new release hardening rather than a new CVE event.
Impact
The release lists what it fixes: root no longer follows symlinks in user home directories, and API key checks now refuse symlinked or out-of-store key files, fail closed on empty client IPs and reject non-string request fields. The notes do not state the exact attack mechanics behind each item, who could have triggered it, or what access was required, so those details remain unknown. The fix target is 1.10.7; the version where each weakness was introduced and the affected ranges are not published. Nothing here shows that every earlier version is vulnerable to every item, that every GHSA was fully closed in 1.10.7, or that 1.10.6 offers no protection.
Who is affected
Relevant if your website sits on a server managed by HestiaCP, especially where several users share the panel, API access is enabled, or backups and restic restores run as root. If you only rent a site, your hosting administrator is the person who acts. The release targets the HestiaCP panel and also changes some bundled dependencies, such as Zlib, the webmail clients and the MariaDB target version. It does not promise coverage of independently packaged runtimes, databases or applications, so those need their own check. Whether the release has been installed or activated depends on how each hosting setup handles updates, so confirm rather than assume.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| HestiaCP | Exact introduced and affected versions for each 1.10.7 hardening item are unknown; do not infer that every earlier version is vulnerable to every item | 1.10.7 is the release target; exact per-change GHSA mapping and prerequisites remain unverified |
Exploitation evidence
Exploitation not established. No established exploitation appears in the reviewed release data. Some items reference GHSA advisories that overlap earlier events, so part of this hardening relates to issues already disclosed. The absence of exploitation reports is not proof that none has occurred.
Actions
- Ask the hosting administrator to confirm which HestiaCP release is both installed and actively running, and that it is a vendor-supported release.
- Treat the move to 1.10.7 as planned maintenance with a tested rollback path and a validated backup, because the release also changes Roundcube, SnappyMail, the MariaDB target, Fail2Ban actions and other dependencies.
- After upgrading, check panel login, API key access, normal web and mail flows, and a test restore, instead of assuming the upgrade commands finished cleanly.
- Review who holds API keys and SSH keys on the server, since deleting a user now also removes their access keys.
- Keep operating system, PHP and application patching on their own schedule and verify their coverage separately, rather than assuming this panel release covers them.
Unknowns
- Which versions introduced each weakness and the exact affected ranges.
- How each GHSA identifier maps to the listed code changes.
- Per-change attack mechanics and prerequisites, such as whether API access or shared panel accounts must be in use.
- Whether any item has been exploited; the reviewed release does not establish exploitation, which is not proof of none.
Sources
- HestiaCP project https://github.com/hestiacp/hestiacp/releases/tag/1.10.7
- HestiaCP project https://api.github.com/repos/hestiacp/hestiacp/releases?per_page=30
Change history
- — Published: Published 14 November 2026 from the HestiaCP 1.10.7 release notes of 13 November 2026, recorded as a security-bearing release with target 1.10.7 and unknown per-change affected ranges.