dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2026-44186

HIGH · 7.3 CVSS v3.1 Published 2026-06-08
Fix available
A fix is available. Upgrade to 2.4.68 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in the mod_proxy_ftp module in Apache HTTP Server with an attacker controlled backend FTP server. This issue affects undefined: from 2.4.0 through 2.4.67. Users are recommended to upgrade to version 2.4.68, which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A vulnerability in Apache HTTP Server's mod_proxy_ftp module allows an attacker-controlled backend FTP server to trigger an infinite loop. When the proxy connects to a malicious FTP server, crafted responses can cause the module to enter an unreachable exit condition, leading to denial of service.

MitigationUpgrade Apache HTTP Server to version 2.4.68 or later. If immediate patching is not possible, restrict mod_proxy_ftp to trusted backend FTP servers only and monitor for hung proxy processes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HTTP ServerWeb server / proxy
Affected:>= 2.4.0, < 2.4.68

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Apache HTTP Server version
    Run 'httpd -v' or 'apache2 -v' to get the server version. Alternatively, check the package manager (e.g., 'rpm -q httpd', 'dpkg -l apache2').
    Affected if Version is >= 2.4.0 and < 2.4.68
  2. Verify if mod_proxy_ftp module is loaded
    Run 'httpd -M' or 'apache2ctl -M' and look for 'proxy_ftp_module' in the loaded modules list. Alternatively, check for 'LoadModule proxy_ftp_module' in httpd.conf or included configuration files.
    Affected if mod_proxy_ftp is loaded and enabled
  3. Check for FTP proxy configuration
    Search configuration files (httpd.conf, included .conf files) for 'ProxyPass' or 'ProxyPassMatch' directives with 'ftp://' URLs. Run: 'grep -r "ProxyPass.*ftp://" /etc/httpd/ /etc/apache2/'
    Affected if ProxyPass or ProxyPassMatch directives point to ftp:// backend servers
  4. Identify all proxy-related directives using FTP protocol
    Search for any 'Proxy*' directives with ftp:// scheme, including 'ProxyRemote', 'NoProxy', or RewriteRule patterns that proxy to FTP backends.
    Affected if Any active proxy configuration forwards requests to backend FTP servers

The environment is affected if Apache HTTP Server version is < 2.4.68 AND mod_proxy_ftp is loaded AND the server is configured to proxy FTP connections to backend servers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.68 or later
Fixed in 2.4.68
Interim mitigation

Upgrade Apache HTTP Server to version 2.4.68 or later. If immediate patching is not possible, restrict mod_proxy_ftp to trusted backend FTP servers only and monitor for hung proxy processes.

Recommended fix High confidence

2.4.68

  1. 1. Identify the current Apache HTTP Server version (e.g., httpd -v or apache2 -v).
  2. 2. Confirm the installed version is between 2.4.0 and 2.4.67 (vulnerable range).
  3. 3. Download Apache HTTP Server version 2.4.68 from the official Apache distribution site (httpd.apache.org) or your system's package manager.
  4. 4. Install the new version following standard procedures for your operating system (compiling from source or using package manager).
  5. 5. Verify the mod_proxy_ftp module is included in the installation.
  6. 6. Test the configuration syntax: httpd -t or apachectl configtest.
  7. 7. Restart the Apache HTTP Server to load the new version.
  8. 8. Confirm the server is running the fixed version (2.4.68) after restart.
Caveat Minor: Review mod_proxy_ftp configuration for any deprecated directives; standard upgrade testing recommended

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in HTTP Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44186 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44186 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data