CVE-2026-43634

HestiaCP 1.2.0-1.9.4 IP Spoofing via CF-Connecting-IP Header

Published May 19, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
HestiaCP versions 1.2.0 through 1.9.4 contain an IP spoofing vulnerability that allows unauthenticated remote attackers to bypass authentication security controls by supplying an arbitrary IP address in the CF-Connecting-IP HTTP header without verifying the request originated from Cloudflare's network. Attackers can exploit this to circumvent fail2ban brute-force protection, bypass per-user IP allowlists, and poison authentication audit logs by spoofing trusted IP addresses on each request.

Analysis

AI-generated

Technical impact

HestiaCP versions 1.2.0 through 1.9.4 can be tricked into accepting an arbitrary CF-Connecting-IP header value when verifying user authentication. This allows an unauthenticated attacker to convince the system that a request comes from a trusted IP address, thereby bypassing authentication controls, disabling fail2ban protections, evading per‑user IP allowlists, and corrupting audit logs. The weakness is classified as CWE‑348, a type of spoofing flaw that permits malicious actors to masquerade as legitimate network addresses.

Affected Systems

The vulnerability affects HestiaCP installations running any version between 1.2.0 and 1.9.4 inclusive. Systems maintain a web‑based control panel and rely on the CF-Connecting-IP header to determine the client IP for authentication and auditing purposes.

Risk and Exploitability

The CVSS score of 8.7 indicates a high severity for this flaw. The EPSS score is not available, so the current probability of exploitation cannot be quantified, and the vulnerability is not listed in the CISA KEV catalog. Attackers can exploit it by sending crafted HTTP requests with a manipulated CF-Connecting-IP header over the Internet, assuming they can reach the HestiaCP service. No authentication or privileged credentials are required; the vulnerability is exploitable from outside the target network.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade HestiaCP to the latest available release that contains a patch for CF‑Connecting‑IP header validation.
  • Modify the HestiaCP authentication logic to accept the CF‑Connecting‑IP header only when the request originates from the Cloudflare IP ranges, or disable the header entirely if Cloudflare is not used.
  • Enforce network‑level restrictions so that only Cloudflare IP addresses can reach the HestiaCP service and strip or reject any CF‑Connecting‑IP header on non‑Cloudflare traffic.

Generated by OpenCVE AI on May 19, 2026 at 15:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Hestiacp
Hestiacp hestiacp
Vendors & Products Hestiacp
Hestiacp hestiacp
Type Values Removed Values Added
Description HestiaCP versions 1.2.0 through 1.9.4 contain an IP spoofing vulnerability that allows unauthenticated remote attackers to bypass authentication security controls by supplying an arbitrary IP address in the CF-Connecting-IP HTTP header without verifying the request originated from Cloudflare's network. Attackers can exploit this to circumvent fail2ban brute-force protection, bypass per-user IP allowlists, and poison authentication audit logs by spoofing trusted IP addresses on each request.
Title HestiaCP 1.2.0-1.9.4 IP Spoofing via CF-Connecting-IP Header
Weaknesses CWE-348
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-348

    Use of Less Trusted Source

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 8, 2026, 2:03 PM
Reserved
May 1, 2026, 6:22 PM
Status
Deferred
Published
May 19, 2026, 3:16 PM
Modified
Jul 24, 2026, 12:10 PM