HestiaCP before 1.10.5 contains an authorization bypass vulnerability that allows non-ROOT_USER administrators to perform write actions while impersonating the protected ROOT_USER account. Attackers can log in via the loginas parameter and POST to /add/cron/, because the read-only flag is never checked, causing crond to run their commands as the protected administrator's system account.
CVE-2026-111627
HIGHPre-NVD 7.27.2Trending — 3 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-10-16. The CNA's CVSS baseline 7.2; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, GitHub Security Advisory
7.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.2Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.2
- EG Score
- 7.2HIGHhigh confidence
- EG Risk
- 32EG Risk 32/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity72% × 45%The EG Score, 7.2 of 10.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 16, 2026
Last Modified
October 16, 2026
Advisory Details (6)
Auto-updated Oct 16, 2026Patch available. Sources: github, github_commit, github_release.
Web page
HestiaCP before 1.10.5 Protected Admin Bypass via Cron Job Creation | Advisories | VulnCheck
https://www.vulncheck.com/advisories/hestiacp-before-1.10.5-protected-admin-bypass-via-cron-job-creationGitHub release Patch Available
Service release
Patch available: hestiacp/hestiacp 1.10.5
https://github.com/hestiacp/hestiacp/releases/tag/1.10.5GitHub commit Patch Available
commit 1af7e057cd5a (hestiacp/hestiacp)
Patch available: hestiacp/hestiacp 1.10.5 (contains commit 1af7e057cd5a)
https://github.com/hestiacp/hestiacp/commit/1af7e057cd5ad2ea945acba6c9932ea1a1802c24Web page
hestiacp/web/inc/policies.php at 1.10.4 · hestiacp/hestiacp · GitHub
https://github.com/hestiacp/hestiacp/blob/1.10.4/web/inc/policies.php#L3-L14Web page
hestiacp/web/add/cron/index.php at 1.10.4 · hestiacp/hestiacp · GitHub
https://github.com/hestiacp/hestiacp/blob/1.10.4/web/add/cron/index.php#L11-L70GitHub advisoryMentions a patch (unverified)
HestiaCP cron job creation endpoint allows an admin (non-ROOT_USER) to add crontab entries on behalf of the protected administrator via impersonation (backend authorization bypass) · Advisory · hestiacp/hestiacp · GitHub
https://github.com/hestiacp/hestiacp/security/advisories/GHSA-vp7q-fjv5-5vg8Vendor Advisories for CVE-2026-111627(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-16 19:42 UTCEG score recompute
- 2026-10-16 19:42 UTCGHSA enrichmentGHSA-8hv6-g9hp-x82m · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-10-16 19:10 UTCEG score recompute
- 2026-10-16 19:09 UTCGHSA enrichmentGHSA-8hv6-g9hp-x82m · GitHub severity HIGH · GitHub CVSS 7.2
- 2026-10-16 18:32 UTCEG score recompute
- 2026-10-16 17:50 UTCEG score recomputeFirst assessed: 7.2 HIGH
- 2026-10-16 17:48 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-111627?
CVE-2026-111627 is a high-severity vulnerability; its CVE record was published on October 16, 2026. HestiaCP before 1.10.5 contains an authorization bypass vulnerability that allows non-ROOTUSER administrators to perform write actions while impersonating the protected ROOTUSER account. Attackers can log in via the loginas parameter and POST to /add/cron/, because the read-only flag is never…
When was CVE-2026-111627 made public?
CVE-2026-111627 was made public on September 15, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 16, 2026. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-111627?
CVE-2026-111627 has a CVSS base score of 7.2 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-111627?
A fix for CVE-2026-111627 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-111627 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-111627
Is Your Infrastructure Affected by CVE-2026-111627?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.