External risk intelligence

OpenBSD ldapd Authentication Bypass and Denial of Service Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-103547

The vulnerability affects ldapd, an LDAP daemon which can be network-reachable if configured to listen on public interfaces. However, ldapd is not enabled by default in OpenBSD, and LDAP services are typically deployed within internal network segments or behind firewalls, making public internet exposure less common than for dedicated internet-facing gateways or web applications.

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a critical vulnerability in OpenBSD's `ldapd` service, which handles secure directory access. If exploited, an attacker could potentially impersonate other users by manipulating authentication data. While `ldapd` is not enabled by default, its presence requires attention to ensure proper configuration and potential exposure.

  • Authentication data could be wrongly reused.
  • It allows impersonation if the service is enabled.
  • Confirm if the `ldapd` service is in use.

Attack Path

How an attacker could exploit the issue

An attacker who can reach the `ldapd` service, even without authentication, could potentially impersonate another user. This occurs because delegated authentication results are incorrectly associated with connections that reuse identifiers after a previous connection has closed. If `ldapd` is enabled and exposed, an attacker could exploit this to bind as a different identity, or cause a denial of service.

  • Attacker must be able to reach `ldapd`.
  • Attacker triggers vulnerability by completing a Bind operation.
  • Risk includes impersonation or denial of service.

Live Threat

Current exploitation, exposure, and threat context

When OpenBSD's `ldapd` is enabled and reachable by remote attackers, authentication results could be improperly correlated between connections. This could allow a remote attacker to impersonate another identity by completing a Bind operation.

  • Authentication results could be leaked.
  • Attackers could impersonate other users.
  • Unauthorized access to services may occur.

Operational Fix

Recommended remediation, mitigation, and detection steps

Given that ldapd is not enabled by default and typically resides within internal network segments, ownership likely falls to the system administrators or platform teams managing OpenBSD systems. The first practical step is to determine if ldapd is active and exposed, identify any critical systems using it, and then coordinate with the accountable owner for remediation planning, considering potential vendor involvement for OpenBSD patches.

  • System administrators and platform teams own.
  • Verify ldapd active status and exposure.
  • Plan patching based on system criticality.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is ldapd in OpenBSD?

ldapd is a Lightweight Directory Access Protocol (LDAP) daemon included in OpenBSD. It serves as a directory service, allowing systems to manage and authenticate users or store directory information centrally. While it provides critical directory functionality, it is intentionally disabled by default in OpenBSD installations, meaning it only runs if a system administrator explicitly enables and configures it for their environment.

How does CVE-2026-103547 enable authentication bypass?

This vulnerability involves a weakness classified as CWE-863, which concerns improper authorization. In affected versions of ldapd, authentication results are tracked using file descriptors and message IDs that may be recycled. When a connection closes and a new one reuses these same identifiers, the system can incorrectly associate the previous authentication outcome with the new session, allowing an attacker to bypass standard checks and impersonate another identity.

Does any network request trigger this vulnerability?

No, a simple network request is not sufficient. An attacker must successfully complete a Bind operation against the service. Furthermore, the vulnerability relies on specific timing where a new connection happens to reuse the same internal identifiers as a closed one. If the ldapd service is not running or if the attacker cannot reach the service, this specific authentication reuse cannot occur.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal identifies this as a possible risk, primarily if you have intentionally enabled and exposed the ldapd service to a network. While ldapd is not enabled by default, it becomes a concern if it is reachable via public interfaces. Because LDAP services are often restricted to internal segments or protected by firewalls, public internet exposure is less common for this specific component compared to web gateways.

What should I do first to address this issue?

Start by verifying whether the ldapd service is currently active on your OpenBSD systems. If it is not in use, disabling it is the most effective way to eliminate the risk. If you must run ldapd, identify which systems have it enabled, assess whether it needs to be network-accessible, and prepare to apply the relevant OpenBSD errata patches to remediate the authentication logic flaw.

References