⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 9.5

How to Fix CVE-2026-43633: Deserialization RCE in hestiacp

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 9.5 - Critical
Actively exploited?Not currently listed in CISA KEV
Affected1.9.0 <= 1.9.4
Fixed in854d71b3c1737b0a0d0cc55c926008ffe1f6719b
Type (CWE)CWE-502: Deserialization of Untrusted Data

What is CVE-2026-43633?

CVE-2026-43633 is an unsafe deserialization in hestiacp. The application accepts attacker-controlled serialized objects and reconstructs them without validating their type, so a crafted payload triggers code execution inside the running process. Unauthenticated remote code execution is the typical impact. Vendor description: HestiaCP versions 1.9.0 through 1.9.4 contain a deserialization vulnerability in the web terminal component caused by a session format mismatch between PHP and Node.js that allows unauthenticated remote attackers to achieve root-level code execution. Attackers can inject crafted data into HTTP headers that are processed by the PHP session handler but incorrectly deserialized by the Node.js web terminal component as trusted session values, resulting in arbitrary command execution on systems with the web terminal feature enabled.

Why this CVE matters

Deserialization bugs are a favorite of ransomware operators because they convert a single HTTP request into full code execution on the target host. Public proof-of-concept code for this CVE class typically appears within days of disclosure, and weaponized exploits follow shortly after.

For deployments of hestiacp that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open hestiacp's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-43633

  1. Read the vendor advisory in full: https://mercuryiss.com.au/hestiacp-unauthenticated-rce-ip-spoofing-cve-2026-43633-cve-2026-43634
  2. Upgrade hestiacp to 854d71b3c1737b0a0d0cc55c926008ffe1f6719b or a later version listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Rotate any credentials, API keys, or session tokens that the vulnerable service touched. An unauthenticated RCE-class flaw means anything the process could see should be treated as exposed.
  5. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  6. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Update the npm package


# CVE-2026-43633 affects hestiacp 1.9.0 <= 1.9.4. Fixed in 1.9.4.
# Vendor advisory: https://github.com/hestiacp/hestiacp/commit/854d71b3c1737b0a0d0cc55c926008ffe1f6719b

# 1. Show the currently resolved version inside the project.
npm ls hestiacp

# 2. Update to the patched release named in the advisory.
npm install hestiacp@1.9.4
npm audit fix

# 3. Lock-file enforcement for CI / production.
npm ci

# 4. Verify.
npm ls hestiacp
# The resolved version must match 1.9.4 (or a later patched release).


# Same flow from a Windows admin workstation.
npm install hestiacp@1.9.4
npm ls hestiacp

Verify the fix landed


# CVE-2026-43633 verification checklist.

# 1. Confirm the running version matches 1.9.4 (replace the version probe with
#    the platform-specific command shown above).

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    OpenVAS, Wazuh). The scanner must no longer flag CVE-2026-43633.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl -u <service-name> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# 4. Cross-check the running build against the vendor advisory:
#    https://github.com/hestiacp/hestiacp/commit/854d71b3c1737b0a0d0cc55c926008ffe1f6719b

If you cannot patch immediately

There is no safe runtime mitigation for deserialization flaws beyond removing exposure: block the affected endpoint at a reverse proxy or WAF and restrict access to authenticated, trusted users only. Patch as soon as possible.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unexpected administrator accounts in hestiacp, scheduled tasks or cron jobs you did not create, new files in web-accessible directories, and outbound connections to addresses not in your baseline. Suspicious requests to the vulnerable endpoint immediately followed by successful 200-class responses with unusually large bodies are a strong indicator of exploitation.

Frequently asked questions

Is CVE-2026-43633 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-43633?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Do I need to assume compromise if my hestiacp was internet-facing and unpatched?

For an unauthenticated RCE-class flaw exposed to the public internet during the known exploitation window, yes. Review logs, rotate credentials the process could access, and look for unexpected accounts, scheduled tasks, or outbound connections.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*