# CVE-2026-63045: Apache HTTP Server: mod_proxy_ftp PASV address handling

> An attacker controlling an FTP server can force the Apache proxy to connect to arbitrary internal hosts via crafted PASV responses in forward proxy setups.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** ALPINE-CVE-2026-63045, AZL-106779, BELL-CVE-2026-63045, BIT-apache-2026-63045, DEBIAN-CVE-2026-63045, ECHO-cbf0-cb8c-fdf2, GHSA-6wv6-863r-87j4, MINI-rrcf-jvj8-m4wc, ROOT-OS-DEBIAN-12-CVE-2026-63045, UBUNTU-CVE-2026-63045

## What is CVE-2026-63045?

CVE-2026-63045 is a high-severity server-side request forgery vulnerability in Apache Http Server, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper validation of FTP PASV reply address in mod_proxy_ftp in Apache Software Foundation Apache HTTP Server through 2.4.68 on all platforms allows, in forward proxy configurations, an untrusted FTP server to cause the proxy to open a data connection to an arbitrary third-party host via a crafted PASV response.

Users are recommended to upgrade to version 2.4.69, which fixes this issue.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-63045?

1 open source package ship an affected version, including apache. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apache` | Bitnami | From 2.4.0 | 2.4.69 |

Products: Apache Http Server.

## How do I fix CVE-2026-63045?

Upgrade apache to 2.4.69 or later.

## Is CVE-2026-63045 being exploited?

There is no known exploitation of CVE-2026-63045 in the wild and no public exploit code.

## Other vulnerabilities in Apache Http Server

- [CVE-2021-42013](https://insights.sbomify.com/CVE-2021-42013/): Apache HTTP Server Path Traversal (critical 9.8, exploited in the wild)
- [CVE-2024-38475](https://insights.sbomify.com/CVE-2024-38475/): Apache HTTP Server Improper Escaping of Output (critical 9.1, exploited in the wild)
- [CVE-2021-40438](https://insights.sbomify.com/CVE-2021-40438/): Apache HTTP Server-Side Request Forgery (SSRF) (critical 9.0, exploited in the wild)
- [CVE-2019-0211](https://insights.sbomify.com/CVE-2019-0211/): Apache HTTP Server Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2021-41773](https://insights.sbomify.com/CVE-2021-41773/): Apache HTTP Server Path Traversal (high 7.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63045 and fix it if it is affected.

What it is: CVE-2026-63045 is a high-severity server-side request forgery vulnerability in Apache Http Server, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63045 in the wild and no public exploit code.

Affected packages and fixed versions:
- apache (Bitnami): affected from 2.4.0; fixed in 2.4.69

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63045/ (Markdown: https://insights.sbomify.com/CVE-2026-63045/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63045
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63045
- OSV: https://osv.dev/vulnerability/CVE-2026-63045

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63045/
Summaries are generated and may contain mistakes; the official description above is the record.