dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2026-29167

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-08
Fix available
A fix is available. Upgrade to 2.4.68 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Use After Free vulnerability in Apache HTTP Server with mod_ldap in per-directory configuration This issue affects Apache HTTP Server: from 2.4.0 through 2.4.67. Users are recommended to upgrade to version 2.4.68, which fixes the issue.

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

Use After Free vulnerability in Apache HTTP Server's mod_ldap when used in per-directory configuration contexts. This memory safety flaw can be exploited to achieve remote code execution or cause denial of service.

MitigationUpgrade Apache HTTP Server to version 2.4.68 or later to resolve the Use After Free in mod_ldap per-directory configurations.

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.0, < 2.4.68

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Check Apache HTTP Server version
    Run 'httpd -v' or 'apache2 -v' to get the installed version number
    Affected if The version is between 2.4.0 and 2.4.67 inclusive (versions < 2.4.68)
  2. Verify mod_ldap module is loaded
    Run 'httpd -M' or 'apache2ctl -M' and look for 'ldap_module' in the loaded modules list
    Affected if mod_ldap appears in the loaded modules output
  3. Inspect main Apache configuration for mod_ldap directives in per-directory contexts
    Search configuration files (httpd.conf, apache2.conf, included conf files) for LDAP-related directives (LDAPTrustedClientCert, LDAPTrustedMode, LDAPAuthzProviderMethod, LDAPCompareConnPoolMin, LDAPCompareConnPoolMax) inside <Directory>, <Files>, or <Location> blocks, or in .htaccess files
    Affected if LDAP directives are found within <Directory>, <Files>, or <Location> blocks, or .htaccess files are in use with LDAP configuration
  4. Check for AllowOverride settings that permit LDAP directives in .htaccess
    Look for 'AllowOverride AuthConfig' or 'AllowOverride All' directives in <Directory> blocks that point to directories containing .htaccess files
    Affected if AllowOverride AuthConfig or higher is set for directories that may contain .htaccess files with LDAP configuration

The environment is affected if Apache version is 2.4.0-2.4.67 AND mod_ldap is loaded AND LDAP directives are present in per-directory configuration contexts (<Directory>, <Files>, or .htaccess files).

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.68 or later
Fixed in 2.4.68
Interim mitigation

Upgrade Apache HTTP Server to version 2.4.68 or later to resolve the Use After Free in mod_ldap per-directory configurations.

Recommended fix High confidence

2.4.68

  1. Verify current Apache HTTP Server version (e.g., httpd -v or apache2 -v)
  2. Stop the Apache HTTP Server service
  3. Upgrade Apache HTTP Server to version 2.4.68 using your system's package manager or by compiling from source
  4. Verify the installed version is 2.4.68
  5. Start the Apache HTTP Server service

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29167 — 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-29167 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