Quick answers
- Is CVE-2026-111627 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111627 being exploited in the wild.
- How severe is CVE-2026-111627?
- High severity, with a CVSS score of 7.2, published 16 October 2026.
- Which products and versions are affected?
- HestiaCP before 1.10.5.
- Is there a fix for CVE-2026-111627?
- Yes: fixed in 1.10.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111627 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-111627?
- 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.
How to fix
- Fixed in: 1.10.5
Technical details
The vulnerability is an authorization bypass in the /add/cron/ endpoint that fails to enforce the read-only flag when a non-ROOT_USER administrator attempts to add cron jobs while impersonated as ROOT_USER via the loginas parameter. The v-add-cron-job command executes with the impersonated user's privileges (root), and input validation uses quoteshellarg but lacks authorization checks, allowing arbitrary scheduled command execution.
Affected products
- HestiaCP HestiaCP before 1.10.5
Timeline
- 2026-10-16: disclosed