VYPR
← All advisories
Unrated severityNVD Advisory· Published Jun 8, 2026

CVE-2026-44186

CVE-2026-44186

Description

Apache HTTP Server's mod_proxy_ftp module contains an infinite loop vulnerability exploitable with a controlled backend FTP server.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Apache HTTP Server's mod_proxy_ftp module contains an infinite loop vulnerability exploitable with a controlled backend FTP server.

Vulnerability

A Loop with Unreachable Exit Condition (Infinite Loop) vulnerability exists in the mod_proxy_ftp module of Apache HTTP Server when an attacker controls the backend FTP server. This issue affects versions 2.4.0 through 2.4.67 [1].

Exploitation

An attacker requires control over a backend FTP server to trigger this vulnerability. The exact exploitation steps are not detailed in the available references, but it involves interacting with the mod_proxy_ftp module in a way that leads to the infinite loop condition [1].

Impact

The primary impact of this vulnerability is a denial-of-service condition. An infinite loop can consume server resources, potentially leading to the unavailability of the Apache HTTP Server. The specific privilege level or scope of compromise is not detailed in the available references [1].

Mitigation

Users are recommended to upgrade to Apache HTTP Server version 2.4.68, which was released on 2026-06-08 and fixes this issue [1].

References
  1. Apache HTTP Server 2.4 vulnerabilities

AI Insight generated on Jun 8, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

1
35c6e405390e

cookie reqest header counting (#324)

https://github.com/icing/mod_h2Stefan EissingMay 27, 2026via body-scan
commit
1 file changed · +4 −0
  • mod_http2/h2_util.c+4 −0 modified
    @@ -1708,6 +1708,8 @@ static apr_status_t req_add_header(apr_table_t *headers, apr_pool_t *pool,
              && !ap_cstr_casecmpn("cookie", (const char *)nv->name, nv->namelen)) {
         existing = apr_table_get(headers, "cookie");
         if (existing) {
+            if (!nv->valuelen)
+                return APR_SUCCESS;
             /* Cookie header come separately in HTTP/2, but need
              * to be merged by "; " (instead of default ", ")
              */
@@ -1719,6 +1721,8 @@ static apr_status_t req_add_header(apr_table_t *headers, apr_pool_t *pool,
             apr_table_setn(headers, "Cookie",
                            apr_psprintf(pool, "%s; %.*s", existing,
                                         (int)nv->valuelen, nv->value));
+            /* Treat the merge as an "add" to not escape LimitRequestFields */
+            *pwas_added = 1;
             return APR_SUCCESS;
         }
     }

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

1