Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

NULL Pointer Dereference in Apache HTTP Server mod_dav_lock

IdentifiersCVE-2026-29169CWE-476· NULL Pointer Dereference

CVE-2026-29169 is a NULL pointer dereference vulnerability in the mod_dav_lock module of Apache HTTP Server. It affects Apache HTTP Server 2.4.66 and earlier. A maliciously crafted request can trigger a NULL pointer dereference in mod_dav_lock, causing the affected server process to crash. Apache states that mod_dav_lock is not used internally by mod_dav or mod_dav_fs, and that its only known use case was mod_dav_svn from Apache Subversion versions earlier than 1.2.0. The issue was fixed in the 2.4.x branch in revision r1933354 and released in Apache HTTP Server 2.4.67.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in denial of service through a crash of the Apache HTTP Server process handling the request. Available scoring and vendor context indicate no demonstrated confidentiality or integrity impact; the primary effect is loss of availability. The issue is described as remotely reachable over the network, requiring no privileges and no user interaction, and can cause high availability impact on the affected component.

Mitigation

If you can’t patch tonight, do this now.

As an interim mitigation, unload or remove mod_dav_lock from the Apache configuration if it is not explicitly required. This is particularly practical because Apache states the module is not used internally by mod_dav or mod_dav_fs, and its only known use case was legacy mod_dav_svn support from Apache Subversion versions earlier than 1.2.0. Limiting exposure of affected HTTP services until patching is completed may further reduce risk, but the primary mitigation in the provided content is removal of mod_dav_lock.

Remediation

Patch, then assume compromise.

Upgrade Apache HTTP Server to version 2.4.67 or later, which contains the fix for CVE-2026-29169. If the environment still loads mod_dav_lock and cannot be upgraded immediately, remove or disable mod_dav_lock where it is not required. Apache specifically notes that mod_dav_lock is not used internally by mod_dav or mod_dav_fs, reducing the likelihood that it is needed in most deployments.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.

VALID 0 / 2 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationHttp Serverapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity9

Community discussion across Reddit, Mastodon, and other social sources.