Skip to content
Wednesday, October 14, 2026AboutContactRSS
Vulnerabilities

Critical-Severity Code Injection Flaw in hestiacp Tracked as CVE-2026-108390

A newly published critical vulnerability in hestiacp carries a CVSS score of 9.9. Here is what is affected and how to respond.

Illustration: A cracked server panel lies open, revealing tangled wires and exposed circuit boards inside.
AI-generated illustration: Threat Times

Key points

  • CVE-2026-108390 affects hestiacp.
  • CVSS 9.9 (Critical).
  • No exploitation confirmed yet.

hestiacp is affected by CVE-2026-108390, a code injection that the National Vulnerability Database rates 9.9 out of 10.

At a glance

CVE
CVE-2026-108390
Product
hestiacp
CVSS
9.9 Critical
Weakness
code injection
Exploited
No known exploitation

What is the vulnerability?

The NVD entry states: Hestia Control Panel is a lightweight and powerful control panel for the modern web. From version 1.9.7 through 1.10.4, update_object_value() in func/main.sh does not escape single quotes when writing a custom document-root value to a user's web.conf file, allowing a low-privileged authenticated panel user with a web domain to inject an additional PATH field. When the user invokes the ordinary Search feature, the root-privileged v-search-user-object script loads the forged field through parse_object_kv_list_non_eval(), which permits reserved shell-variable names and globally replaces PATH before invoking column without an absolute path. By placing a malicious column executable in the injected search path, the user can execute arbitrary code as root. This residual vulnerability was introduced when version 1.9.7 replaced the raw eval sink addressed by CVE-2026-84984 with parse_object_kv_li

Affected versions

VendorProductVersions
Hestiacphestiacp>= 1.9.7, < 1.10.5

CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.

Is it being exploited?

There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.

What should you do?

  • Identify whether the affected product and versions run in your environment.
  • Apply the vendor update listed in the advisory as soon as it is available.
  • Limit network exposure of the affected service until it is patched.
  • Monitor the vendor advisory for updated guidance or exploitation reports.

What to do and how to stay safe: CVE-2026-108390

  • Vulnerability severity scores ignore your specific architecture and context.
  • Exploitability depends on network exposure and user behavior, not just code flaws.
  • Prioritization requires continuous asset inventory and threat intelligence alignment.

Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.

Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is CVE-2026-108390?

CVE-2026-108390 is a code injection vulnerability in hestiacp.

How severe is CVE-2026-108390?

It has a CVSS score of 9.9 Critical.

Is CVE-2026-108390 being exploited?

There is no public confirmation of exploitation at the time of publication.

Sources

  1. NVD — CVE-2026-108390
  2. Reference
  3. Reference
CVE-2026-108390hestiacpCritical severity
Related articles