Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-29167 – Use After Free in mod_ldap – Apache HTTP Server 2.4.0 through 2.4.67

Be the first to know when new zero-days emerge:

Summary

CVE-2026-29167 is a Use After Free vulnerability (CWE-416) in the mod_ldap module of Apache HTTP Server, triggered when mod_ldap is configured in per-directory mode. It affects all Apache HTTP Server releases from 2.4.0 through 2.4.67 and carries a CVSS v3.1 base score of 9.8 (Critical), reflecting full compromise of confidentiality, integrity, and availability exploitable by unauthenticated remote attackers. A fix is available in Apache HTTP Server 2.4.68, released June 8, 2026.

Technical details

  • Root cause: A use-after-free memory safety flaw (CWE-416) in the mod_ldap module — memory that has been freed is subsequently accessed, leading to memory corruption.
  • Trigger condition: The vulnerability is present when mod_ldap is configured at the per-directory level, for example via <Directory> blocks or .htaccess files enabling LDAP-based authentication on specific paths.
  • Attack vector: Network-accessible with no authentication and no user interaction required (AV:N/AC:L/PR:N/UI:N), allowing unauthenticated remote attackers to trigger the flaw over standard HTTP/HTTPS.
  • Impact: Full compromise of confidentiality, integrity, and availability (C:H/I:H/A:H), consistent with the severe outcomes of exploitable use-after-free memory corruption.

Affected software

  • Apache HTTP Server 2.4.0 through 2.4.67 (inclusive), when mod_ldap is configured in per-directory mode.

Severity

CVSS v3.1 base score: 9.8 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate action: Upgrade to Apache HTTP Server 2.4.68, released June 8, 2026, which resolves this vulnerability (fix committed as revision r1934935 on June 3, 2026).
  • If immediate patching is not feasible: Disable the mod_ldap module or remove per-directory LDAP configuration directives until the upgrade can be applied to eliminate the vulnerable code path.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge