Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-42535 – DAV Property Database Manipulation and Denial of Service – Apache HTTP Server 2….

Be the first to know when new zero-days emerge:

Summary

CVE-2026-42535 is a critical path handling vulnerability in the mod_dav_fs module of Apache HTTP Server, affecting all versions through 2.4.67. The flaw is classified as CWE-668 (Exposure of Resource to Wrong Sphere) and allows a WebDAV content author to directly manipulate trusted DAV property databases and crash child processes. With a CVSS v3.1 score of 9.1 (Critical), the vulnerability is network-accessible, requires no privileges, and no user interaction, making internet-facing WebDAV-enabled Apache deployments a direct target.

Technical details

  • Root cause: A path handling flaw in mod_dav_fs (CWE-668: Exposure of Resource to Wrong Sphere) allows improperly resolved file paths to reach and modify trusted DAV property database files that should be inaccessible to content authors.
  • Trigger conditions: Exploitable on any Apache HTTP Server deployment where mod_dav_fs is loaded and WebDAV access is enabled; a WebDAV content author — including anonymous users on open WebDAV deployments — can issue crafted WebDAV requests to trigger the flaw.
  • Attack vector: Network-accessible (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction needed (UI:N).
  • Impact: Successful exploitation allows direct manipulation of trusted server-side DAV property databases (Integrity: High) and causes Apache child worker process crashes (Availability: High); there is no direct confidentiality impact (C:N).

Affected software

  • Apache HTTP Server versions 0 through 2.4.67 with mod_dav_fs (WebDAV) enabled

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to Apache HTTP Server 2.4.68, released June 8, 2026, which contains the fix (commit r1935013). This is the only vendor-recommended remediation; no alternative workarounds are offered.
  • If immediate patching is not possible, consider restricting access to WebDAV endpoints at the network perimeter or via Apache <Location> directives to limit exposure to trusted clients only.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge