CVE-2026-59685·Apache vulnerability
Out-of-bounds Write vulnerability in Apache HTTP Server on Windows while processing paths with 8.3 names that may grow when expanded. This issue affects Apache HTTP Server: from 2.4.0 through 2.4.68.
- Severity
- high
- Software
- Apache
- Fixed in
- 2.4.69
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.50% — higher than 41% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-59685 scores 7.5 on CVSS, so a successful attack would be serious — but at 0.50%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 2.4.0
Until: 2.4.69
Fixed in: 2.4.69
How to fix this CVE
Apache HTTP Server versions 2.4.0 through 2.4.68 contain a memory safety vulnerability in Windows path processing that could allow information disclosure. Upgrade to Apache 2.4.69 or later immediately to patch the out-of-bounds write condition triggered by DOS 8.3 filename expansion. Verify the update completes successfully and restart the Apache service to ensure the patched version is running.
sudo dnf update -y httpd; sudo systemctl restart httpdDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check Apache version with `apache2 -v` (Ubuntu/Debian) or `httpd -v` (RHEL/CentOS/Amazon Linux) and confirm it is 2.4.69 or later
- Step 2: Verify the installed package version with `apt show apache2` (Debian-based) or `dnf list installed httpd` (RPM-based) to confirm patch level
- Step 3: Search Apache error logs (`/var/log/apache2/error.log` or `/var/log/httpd/error_log`) for segmentation faults or memory access violations occurring in mod_core or path processing modules
- Step 4: After upgrade, restart Apache with `sudo systemctl restart apache2` or `sudo systemctl restart httpd`, then confirm service is running and listening with `sudo ss -tulpn | grep :80`
FAQ
What is CVE-2026-59685?
This vulnerability is an out-of-bounds memory write in Apache HTTP Server's Windows path handling routines when processing DOS 8.3 format filenames that expand beyond their short-name representation. On affected Windows systems, this can lead to information disclosure.
Is CVE-2026-59685 being actively exploited?
No, this vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploit code is currently available. However, it should still be patched promptly due to its high CVSS score of 7.5.
What versions of Apache are affected by CVE-2026-59685?
Apache HTTP Server versions 2.4.0 through 2.4.68 are vulnerable. The vulnerability is fixed in version 2.4.69 and later.
How do I check if my server is vulnerable to CVE-2026-59685?
Run `apache2 -v` or `httpd -v` and check the version number. If it shows 2.4.68 or earlier, your server is vulnerable and requires immediate patching.
Does Defensia detect CVE-2026-59685?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Apache is installed on a monitored server, CVE-2026-59685 will appear in your dashboard with remediation steps.
Related Apache CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-59685. Free for 1 server.
Get started free