dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2026-29169

HIGH · 7.5 CVSS v3.1 Published 2026-05-04
Fix available
A fix is available. Upgrade to 2.4.67 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A NULL pointer dereference in mod_dav_lock in Apache HTTP Server 2.4.66 and earlier may allow an attacker to crash the server with a malicious request.mod_dav_lock is not used internally by mod_dav or mod_dav_fs. The only known use-case for mod_dav_lock was mod_dav_svn from Apache Subversion earlier than version 1.2.0. Users are recommended to upgrade to version 2.4.66, which fixes this issue, or remove mod_dav_lock.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A NULL pointer dereference vulnerability in mod_dav_lock module of Apache HTTP Server 2.4.66 and earlier allows remote attackers to crash the server via malicious requests. The mod_dav_lock module has extremely limited use, only supporting Apache Subversion versions prior to 1.2.0, making this a low-footprint attack vector.

MitigationUpgrade to Apache HTTP Server 2.4.66 or remove the mod_dav_lock module from the server configuration if not needed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HTTP ServerWeb server / proxy
Affected:< 2.4.67

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Apache HTTP Server version
    Run 'httpd -v' or 'apache2 -v' to obtain the server version number
    Affected if Version is 2.4.66 or earlier (any version less than 2.4.67)
  2. Identify if mod_dav_lock is compiled as a static module
    Run 'httpd -l' or 'apache2 -l' to list compiled-in modules and look for mod_dav_lock.c in the output
    Affected if mod_dav_lock appears in the compiled module list
  3. Identify if mod_dav_lock is loaded as a dynamic module
    Check for 'LoadModule dav_lock_module' in httpd.conf, apache2.conf, or included configuration files in the conf directory
    Affected if The LoadModule directive for dav_lock is present and uncommented
  4. Check if mod_dav_lock is actively used in configuration
    Search all configuration files for 'DAV' directives, particularly 'DAV lock' or references to lock databases, which indicate mod_dav_lock is in use
    Affected if DAV lock or lock-related directives are configured and the module is loaded

A user is affected if they run Apache HTTP Server version 2.4.66 or earlier AND have the mod_dav_lock module loaded and actively configured for use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.67 or later
Fixed in 2.4.67
Interim mitigation

Upgrade to Apache HTTP Server 2.4.66 or remove the mod_dav_lock module from the server configuration if not needed.

Recommended fix High confidence

2.4.67

  1. Download Apache HTTP Server version 2.4.67 or later from the official Apache download site (httpd.apache.org)
  2. Compile and install the new version following standard Apache build procedures, or use your system's package manager to upgrade if a packaged version is available
  3. Verify the installation by running 'httpd -v' to confirm the version number
  4. Restart the HTTP Server to load the new version
  5. Optionally, if mod_dav_lock is not needed, consider removing or commenting out 'LoadModule dav_lock_module modules/mod_dav_lock.so' from httpd.conf for defense in depth
Caveat Minor: Ensure any custom configurations for mod_dav_lock are reviewed, though this module had limited use cases (only mod_dav_svn pre-1.2.0)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in HTTP Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29169 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29169 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data