Quick answers
- Is CVE-2026-12196 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-12196 being exploited in the wild.
- How severe is CVE-2026-12196?
- Informational severity, with a CVSS score of 8.3, published 4 July 2026.
- Which products and versions are affected?
- HestiaCP Prior to commit 8be23943c7e3231f66d226ca931c76f93be98412.
- Is there a fix for CVE-2026-12196?
- A patch was published on 2026-06-23: Fix merged into main branch via Pull Request 5440 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-12196 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-12196?
- Check whether you run HestiaCP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A broken access control vulnerability (CWE-287/CWE-285) exists in the HestiaCP web panel due to an improperly implemented authorization check in the cron job management component. The check relies on an undefined variable ($ROOT_USER), causing the logic to fail and allowing low-privileged users to modify 'panel cron jobs' that execute as the privileged panel user. Because the panel user has passwordless sudo access to administrative scripts (e.g., v-change-user-password), an authenticated attacker can schedule a task to reset the administrator's password or execute other management commands. The vulnerability is further exacerbated by a lack of CSRF validation on the affected endpoint. A fix was introduced in commit 8be2394.
Affected products
- HestiaCP HestiaCP Prior to commit 8be23943c7e3231f66d226ca931c76f93be98412
Timeline
- 2026-06-23: patched: Fix merged into main branch via Pull Request 5440
- 2026-07-04: disclosed: Public advisory and blog post published
- 2026-07-04: advisory: NVD entry published