CVE Tools

CVE-2026-42528

Apache HTTP Server: mod_dav shared lock overflow

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

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.68Upgrade to: after 2.4.68Stated 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 server runs Apache HTTP Server with mod_dav (WebDAV) enabled and whether any user, including low-privilege accounts, can create WebDAV locks.
  2. If you don't use WebDAV at all, disable the mod_dav module as an immediate safeguard.
  3. Upgrade Apache HTTP Server to version 2.4.69 or later, which fixes this issue.
  4. Restart the web server after upgrading and confirm the service comes back up and stays stable.

What it is

From the CVE record

A memory calculation bug in mod_dav in Apache httpd 2.4.67 and earlier allows an attacker with permission to create WebDAV locks to crash server child processes. Users are recommended to upgrade to version 2.4.69, which fixes this issue

In plain language

Written by AI from the record

A bug in Apache HTTP Server's WebDAV feature lets someone who already has permission to create file locks crash the server's worker processes, so if you use Apache with WebDAV enabled you should update it now.

A memory-size calculation error (CWE-789) in Apache httpd's mod_dav module lets an authenticated user with WebDAV lock-creation rights trigger a worker-process crash over the network, affecting versions up to 2.4.67.

If you're affected

  • Website/service outage
  • Repeated crashes under attack
  • Operational disruption

Exploitation

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

EPSS34th
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.4% chance of exploitation activity in the next 30 days, which ranks it in the 34th percentile of scored CVEs.

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

Lifecycle

8 events over 5 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Publishedweakness classified, record updated, record updated

Affected products

Technical detail

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

Scored 4.3 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 LowRequires basic user-level privileges
  • 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 NoneNo integrity impact
  • Availability LowReduced performance or intermittent disruption of service

Weaknesses

Sources

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.