CVE-2026-43634: HestiaCP 1.2.0-1.9.4 IP Spoofing via CF-Connecting-IP Header
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.
Security readout for executives and security teams
Plain-English summary
HestiaCP trusted a Cloudflare client-IP header without confirming the request actually came through Cloudflare. An internet attacker could make login-related requests appear to come from chosen IP addresses, weakening brute-force blocking, IP allowlists, and audit trails.
Executive priority
Treat as high priority for internet-facing control panels. The issue may not directly grant code execution, but it can undermine login defenses and audit reliability during attacks.
Technical view
CVE-2026-43634 affects HestiaCP 1.2.0 through 1.9.4. The application accepts arbitrary CF-Connecting-IP values without validating Cloudflare source networks, enabling unauthenticated remote IP spoofing against authentication security controls. Sources cite CWE-348 and CVSS 4.0 score 8.7.
Likely exposure
Exposed HestiaCP admin interfaces are most at risk, especially where fail2ban, per-user IP allowlists, or authentication investigations rely on logged client IPs.
Exploitation context
The source bundle includes technical/exploit-labeled references, but KEV is false and no provided source confirms active exploitation in the wild.
Researcher notes
Evidence supports unauthenticated network exploitation for IP spoofing, not confirmed real-world exploitation. The provided bundle references a patch commit, GitHub issue, PR, CVE record, and third-party advisory; fixed release details should be confirmed from HestiaCP guidance.
Mitigation direction
Review HestiaCP vendor issue, PR, and patch guidance immediately.
Upgrade or patch to code that fixes CF-Connecting-IP trust handling.
Restrict HestiaCP admin access to trusted networks or VPNs.
Trust proxy client-IP headers only from verified Cloudflare source networks.
Review authentication controls that depend on client IP address.
Validation and detection
Inventory HestiaCP versions and flag 1.2.0 through 1.9.4.
Confirm patched code validates Cloudflare origin before using CF-Connecting-IP.
Review logs for CF-Connecting-IP use from non-Cloudflare sources.
Check authentication logs for inconsistent or suspicious client IP patterns.
Verify fail2ban and allowlist decisions use trustworthy client IP data.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-348: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-348 · source CWE mapping
Use of Less Trusted Source
Use of Less Trusted Source represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.