Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-58415 Overview
CVE-2026-58415 is an information disclosure vulnerability in mod_dav_fs within the Apache HTTP Server. The flaw allows a remote, unauthenticated client to read WebDAV dead properties of resources it does not have authoring permissions for. Exploitation requires only a GET request against the .DAV state directory, which stores internal WebDAV metadata on the filesystem. The issue affects Apache HTTP Server versions 2.4.0 through 2.4.68 on all platforms and is addressed in version 2.4.69. The weakness is tracked under CWE-552: Files or Directories Accessible to External Parties.
Critical Impact
Remote attackers can retrieve WebDAV dead properties over the network without authentication, exposing metadata that should remain internal to the server.
Affected Products
- Apache HTTP Server 2.4.0 through 2.4.68 with mod_dav_fs enabled
- All operating system platforms running affected Apache HTTP Server versions
- WebDAV deployments that expose the .DAV state directory through the web root
Discovery Timeline
- 2026-10-01 - CVE-2026-58415 published to the National Vulnerability Database
- 2026-10-05 - Last updated in NVD database
Technical Details for CVE-2026-58415
Vulnerability Analysis
The Apache HTTP Server mod_dav_fs module implements the filesystem backend for WebDAV. It persists dead properties, lock state, and other WebDAV metadata inside a .DAV state directory on the server filesystem. In versions prior to 2.4.69, Apache does not restrict external GET requests from reaching files inside this directory. A remote client can therefore request the state files directly over HTTP and read WebDAV dead properties attached to resources the client is not authorized to author. The disclosed data is limited to WebDAV metadata, which aligns with the confidentiality-only impact classification.
Root Cause
The root cause is a missing access control on an internal state directory. mod_dav_fs stores operational data inside the document root hierarchy without configuring Apache to deny external access to the .DAV path. Any request routed through the normal request pipeline is served as a static file, bypassing the WebDAV authorization logic that would otherwise gate access to the underlying resources.
Attack Vector
Exploitation is performed over the network with no authentication, no user interaction, and low attack complexity. An attacker sends a GET request to the .DAV directory path within a WebDAV-enabled virtual host. The server returns the raw state file contents, revealing dead properties stored for one or more resources. The attacker does not need write or authoring privileges on the targeted resources. The vulnerability does not permit modification of data or disruption of service, so impact is scoped to information disclosure. No public proof-of-concept exploit, Exploit-DB entry, or CISA KEV listing exists at the time of publication. The EPSS probability is 0.533% at the 43.216 percentile as of 2026-10-08.
Detection Methods for CVE-2026-58415
Indicators of Compromise
- HTTP GET requests in Apache access logs targeting paths that contain .DAV or /.DAV/ segments on WebDAV-enabled virtual hosts.
- Successful 200 OK responses for requests to internal state files that should not be served to external clients.
- Unusual retrieval of files with WebDAV property extensions originating from external IP addresses.
Detection Strategies
- Review Apache HTTP Server access logs for requests matching the regex pattern /\.DAV(/|$) and alert on any response code other than 403 or 404.
- Audit httpd.conf and included configuration fragments for <Directory> or <Location> blocks that fail to deny access to .DAV paths.
- Correlate WebDAV PROPFIND traffic with subsequent GET requests from the same source to identify reconnaissance patterns.
Monitoring Recommendations
- Forward Apache access and error logs to a centralized analytics platform and build detections for .DAV directory access attempts.
- Monitor outbound responses from WebDAV endpoints for unexpected content types or file extensions associated with internal state storage.
- Track Apache HTTP Server version inventory and flag any host running 2.4.0 through 2.4.68 with mod_dav_fs loaded.
How to Mitigate CVE-2026-58415
Immediate Actions Required
- Upgrade Apache HTTP Server to version 2.4.69 or later on all hosts where mod_dav_fs is enabled.
- Inventory virtual hosts that load mod_dav and mod_dav_fs to confirm patch coverage across the environment.
- Review historical access logs for prior GET requests against .DAV paths and treat matches as potential disclosure events.
Patch Information
The Apache HTTP Server project fixed the issue in version 2.4.69. Administrators should obtain the updated release and track status through the Apache HTTP Server Vulnerabilities advisory page. Additional disclosure context is available in the Open Wall OSS Security Post.
Workarounds
- Add an explicit <DirectoryMatch> or <LocationMatch> block in Apache configuration that denies all access to paths matching \.DAV until patching is complete.
- Place a reverse proxy or web application firewall rule in front of WebDAV endpoints to block requests whose URI path includes .DAV.
- Relocate the WebDAV DavLockDB and state storage outside the document root where supported by the deployment.
# Configuration example: deny external access to the .DAV state directory
<LocationMatch "/\.DAV(/|$)">
Require all denied
</LocationMatch>
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

