HestiaCP 1.10.8: local 2FA QR generation and three maintainer advisories on backup access, impersonation redirect and reset logging
Identifiers: HestiaCP-1.10.8-security-release · GHSA-784f-pcj8-rqxp · GHSA-76m3-mq7g-jc97 · GHSA-4qc9-p3qr-434q
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
HestiaCP published release 1.10.8 on 18 November 2026. Its Security section lists three changes: 2FA QR codes are now generated locally with bacon/bacon-qr-code 3.1.1 instead of through an external QR service, and the panel refuses to save a broken 2FA secret (#5869); the post-login redirect now stays within the panel (#5990); and users can only download their own backup archives, not other files that merely start with their username (#5990). The release also bundles Nginx 1.30.7 and SnappyMail 3.1.3, adds a Hestia-specific Dovecot Fail2Ban filter with maxretry 10, and makes the password and 2FA reset pages opened from an email link always carry a CSRF token. On 19 November 2026 the maintainers published three advisories that link to these changes: GHSA-784f-pcj8-rqxp on cross-account backup access, GHSA-76m3-mq7g-jc97 on an open redirect during legitimate admin impersonation, and GHSA-4qc9-p3qr-434q on failed reset logging and rate limiting. A later 1.10.9 release carries a security-bearing PHP runtime update that is tracked as a separate PHP incident. Checked as of 20 November 2026.
Impact
According to the release notes, earlier panel QR generation sent the 2FA secret through an external QR service. That describes an exposure path to an outside party for enrollments that used that flow. No storage or misuse of any secret is known, no advisory maps to it, and the notes give no completed affected range. GHSA-784f-pcj8-rqxp describes an authenticated panel user with a particular legacy overlapping username being able to reach another user's backup; the maintainers report a laboratory reproduction in which one user's backup archive was accessed by another, a specific cross-account exposure rather than access to arbitrary host files. GHSA-76m3-mq7g-jc97 describes an open redirect in the flow where an administrator legitimately accesses the panel as a user; it requires a valid active admin session and the relevant tokens, and the risk includes the panel CSRF token being exposed to the redirect target. It does not let an outsider impersonate an administrator. GHSA-4qc9-p3qr-434q describes failed password and 2FA reset attempts not being logged or rate-limited as intended, with item-specific conditions; this weakens detection and slows blocking of guessing, and the maintainers report a laboratory reproduction. This generic reset-failure logging is distinct from the new Dovecot Fail2Ban filter, which concerns mail logins.
Who is affected
GHSA-784f-pcj8-rqxp lists affected <1.10.7 and fixed 1.10.8; the notice does not settle how 1.10.7 behaves for this bug. GHSA-76m3-mq7g-jc97 lists affected 1.10.7 and fixed 1.10.8. GHSA-4qc9-p3qr-434q lists affected 1.10.7 and fixed 1.10.8, but its description reports a reproduction on 1.10.5, so the published range and the reproduction differ and the exact earlier range is uncertain. The 2FA QR change carries no completed affected range and no advisory. Relevance also depends on workflow: the 2FA item matters where accounts enrolled 2FA through the panel QR code, the redirect item concerns administrators who access the panel as a user, the backup item concerns panel users who download backups on hosts with legacy overlapping usernames, and the reset item concerns the password and 2FA reset pages. 1.10.8 is the containing fix; use a supported vendor update that includes it. A new panel version number does not by itself show that bundled or separate runtimes were patched, and no other package fix should be inferred from the 1.10.9 release title.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| HestiaCP panel (external QR generation) | Earlier versions using the external QR workflow; exact range unspecified | 1.10.8 |
| HestiaCP backup downloads | <1.10.7 according to advisory; behavior on 1.10.7 not established | 1.10.8 |
| HestiaCP admin redirect | 1.10.7 according to advisory | 1.10.8 |
| HestiaCP reset logging | 1.10.7 listed; lab reproduction on 1.10.5; exact earlier range unknown | 1.10.8 |
Exploitation evidence
Exploitation not established. The Hestia advisories report maintainer laboratory reproductions for the backup access and reset logging items, including one showing cross-account backup access; the reviewed text does not report a comparable reproduction for the redirect item. None reports attacks in the wild, and the release notes make no statement about exploitation. These are attributed laboratory findings and publisher silence, not confirmation that no attacks occurred.
Actions
- Take a protected backup for recoverability, then upgrade through the normal Hestia update path to a supported release that contains 1.10.8, and have the owner or operator validate the panel afterwards.
- Review which admin or user accounts enrolled 2FA through the panel QR code on earlier versions. Decide whether a controlled re-enrollment is warranted; verify recovery access first and avoid a blanket 2FA reset that could lock the owner out.
- Review historical backup download activity, admin access to user accounts and reset attempts in panel logs for the relevant periods, especially on hosts that ever had overlapping legacy usernames, and treat findings as leads for the host administrator rather than proof of compromise.
- After upgrading, confirm the running nginx version and other runtimes on the host separately; the bundled 1.30.7 target does not prove separate nginx containers or site stacks were updated.
- Check that the dovecot-iptables Fail2Ban jail now matches mail login failures, and separately confirm that failed password and 2FA reset attempts are being logged by the panel.
- Test normal administrative workflows after the update: admin login, accessing the panel as a user, password and 2FA reset from an email link, backup download and webmail on SnappyMail 3.1.3.
- Track the 1.10.9 PHP runtime update under the separate PHP incident and confirm panel and runtime versions individually.
Unknowns
- Which earlier versions used the external QR path, and which installations or enrollments actually used it; the notes give no completed affected range and no advisory covers it.
- Whether the external QR service retained or logged any submitted secrets; no storage or misuse is known.
- Whether 1.10.7 is affected by the backup access issue in GHSA-784f-pcj8-rqxp, and how far back the reset logging issue in GHSA-4qc9-p3qr-434q extends, given the 1.10.5 reproduction.
- Whether any installation was actually targeted; the advisories describe laboratory reproductions for the backup and reset items and establish no in-the-wild evidence.
Sources
- HestiaCP project https://api.github.com/repos/hestiacp/hestiacp/releases/tags/1.10.8
- HestiaCP project https://github.com/hestiacp/hestiacp/releases/tag/1.10.9
- HestiaCP project https://github.com/hestiacp/hestiacp/security/advisories/GHSA-784f-pcj8-rqxp
- HestiaCP project https://github.com/hestiacp/hestiacp/security/advisories/GHSA-76m3-mq7g-jc97
- HestiaCP project https://github.com/hestiacp/hestiacp/security/advisories/GHSA-4qc9-p3qr-434q
Change history
- — Published: 19 November 2026: Published briefing for HestiaCP 1.10.8, released 18 November 2026, covering local 2FA QR generation, login redirect restriction, and own-backup download scope. Earlier 1.10.7 and 1.10.6 records are unchanged.
- — Updated: 20 November 2026: record updated with the three maintainer advisories of 19 November 2026, GHSA-784f-pcj8-rqxp on cross-account backup access, GHSA-76m3-mq7g-jc97 on an open redirect during legitimate admin impersonation and GHSA-4qc9-p3qr-434q on reset failure logging, all fixed in the containing release 1.10.8, with the 2FA QR item and the separate 1.10.9 PHP runtime update kept distinct.