CVE Tools

CVE-2026-42535

Apache HTTP Server: mod_dav_fs protected directory access

CVE-2026-42535 affects Apache HTTP Server (CVSS 9.1, Critical).

No known exploitation. EPSS puts it in the 46th percentile. A vendor fix is available.

Check it yourself

OpenVAS · 48 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.157088

Run the check

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Apache Software Foundation Apache HTTP ServerAffected: ≤ 2.4.67Upgrade to: after 2.4.67Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether your Apache configuration uses mod_dav_fs / WebDAV (for example, any enabled WebDAV filesystem/DAV directives or mounts).
  2. Determine your current Apache HTTP Server version.
  3. Upgrade Apache HTTP Server to 2.4.68 (this is the fixed version).
  4. If you cannot upgrade immediately, disable or restrict WebDAV (mod_dav_fs) so the vulnerable code path is not reachable, and plan an upgrade as soon as possible.

What it is

From the CVE record

A path handling issue in mod_dav_fs in Apache 2.4.67 and earlier allows a WebDAV content author to directly manipulate trusted DAV property databases, potentially causing child process crashes. Users are recommended to upgrade to version 2.4.68, which fixes this issue.

In plain language

Written by AI from the record

This is a serious bug in Apache HTTP Server that could let a remote attacker crash the web server without any login by abusing WebDAV features; if you use WebDAV (mod_dav_fs), you should act.

CVE-2026-42535 is an unauthenticated denial-of-service in Apache HTTP Server’s mod_dav_fs where a network attacker can manipulate WebDAV properties to corrupt/alter the DAV property database, potentially crashing child processes.

If you're affected

  • Web site outage
  • Loss of customer access
  • Service disruption
  • Potential cascading downtime

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS46th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.5% chance of exploitation activity in the next 30 days, which ranks it in the 46th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 45 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. OpenVAS check added
  3. Patch availablerecord updated
  4. Publishedweakness classified

Affected products

Scale

How widely the affected products are used. This is not a count of vulnerable hosts.

Estimate Public sources, each figure dated. How much of it is already patched is not known.

Apache HTTP Server

Web
  • 21%of websites

    Among websites whose web server we know.

    W3Techs ↗ · as of 2 Nov 2026 · Medium confidence

Version split · W3Techs · as of 2 Nov 2026

  • 2.495%
  • 2.25.1%
  • 1<1%
  • 2.0<1%

Technical detail

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

Scored 9.1 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Questions about CVE-2026-42535

Is CVE-2026-42535 being exploited?
No exploitation is confirmed and no public exploit is known. EPSS puts the chance of exploitation in the next 30 days at 0.5%.
Which versions are affected by CVE-2026-42535?
Apache HTTP Server: ≤ 2.4.67.
How do I fix or mitigate CVE-2026-42535?
The vendor has published a fix. The advisory is on httpd.apache.org.

Last updated

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Apache HTTP Server, not every advisory.