CVE-2026-44186: Apache HTTP Server infinite loop in mod_proxy_ftp

CVE-2026-44186 · Severity: info · Published 2026-06-08

The Apache HTTP Server is a widely used web server for hosting websites and applications. A vulnerability in its FTP proxy module allows a malicious or compromised backend FTP server to trigger an infinite loop on the web server. This can lead to a denial-of-service (DoS) condition, making the web server unresponsive to legitimate users and potentially impacting business operations.

Technologies: Apache HTTP Server. Vendors: Apache.

Quick answers

Is CVE-2026-44186 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-44186 being exploited in the wild.
How severe is CVE-2026-44186?
Informational severity, published 8 June 2026.
Which products and versions are affected?
Apache HTTP Server 2.4.0 through 2.4.67.
Is there a fix for CVE-2026-44186?
A patch was published on 2026-06-05: Fixed in 2.4.x by r1935004 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44186 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-44186?
Check whether you run Apache HTTP Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability exists in the mod_proxy_ftp module of Apache HTTP Server. The flaw is located in the proxy_ftp_handler function and is triggered when the server interacts with an attacker-controlled or malicious backend FTP server. By sending a specifically crafted response, the backend server can cause the Apache process to enter an infinite loop, consuming CPU resources and leading to a denial-of-service (DoS). The issue is fixed in version 2.4.68.

Affected products

  • Apache HTTP Server 2.4.0 through 2.4.67

Timeline

  • 2026-04-27: disclosed: Reported to security team
  • 2026-06-05: patched: Fixed in 2.4.x by r1935004
  • 2026-06-08: advisory: Update 2.4.68 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.