Skip to main content

Apache LDAP API CVE-2026-103552

| EUVDEUVD-2026-91382 HIGH
Stack-based Buffer Overflow (CWE-121)
2026-10-02 apache GHSA-mggr-349m-j697
7.3
CVSS 3.1 · Vendor: apache
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach LDAP service over network
  2. Exploit
    Send deeply nested search filter pre-bind
  3. Execution
    Trigger recursive stack overflow in decoder
  4. Impact
    Crash service and deny availability

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a server-side component that uses the Apache Directory LDAP API (versions 1.2.0 through 1.2.8) to decode client-supplied LDAP search filters, reachable over the network. The critical enabling condition is that the malicious filter is processed 'before binding,' so NO authentication is required. Limiting factors: the target must actually run a vulnerable 1.2.0-1.2.8 version in a decoder/server role that parses untrusted filters, and deployments on 1.2.9 or later, or those not exposing filter decoding to untrusted clients, are not affected. The realistic impact is service crash (availability), which bounds the damage versus a code-execution flaw.

Impact

No CVSS vector, EPSS score, KEV listing, or public POC was provided in the input, so quantitative exploitation signals are entirely absent and the assessment rests on the description and CWE-121 alone. The description is favorable to an attacker on access terms: the malicious deeply nested search filter is sent 'before binding,' meaning no authentication is required, and LDAP is a network-facing protocol - so the reachability profile is network, low-complexity, unauthenticated. However, the technical impact is most plausibly a denial of service: a 'deeply nested search filter that overflows the stack in the server's decoder' describes recursion-driven stack exhaustion, which typically crashes the parsing process rather than yielding code execution, despite the CWE-121 (stack-based buffer overflow) label. Net real-world risk is moderate: easy to trigger remotely without credentials, but the outcome is availability loss rather than confidentiality/integrity compromise, and the affected component is a specific Java library rather than a ubiquitous platform. This is a patch-worthy availability issue for exposed deployments, not a critical RCE - though note the CWE-121 classification leaves a residual, unconfirmed possibility of memory corruption beyond a simple crash that should be verified with the Apache advisory. Exploitation status: no public exploit identified at time of analysis.

Exploit ScenarioDerived

An unauthenticated attacker with network reachability to a service that uses the Apache Directory LDAP API to decode incoming LDAP search requests sends a single search operation containing a filter nested to extreme depth, before any bind/authentication occurs. The vulnerable decoder recurses through the nested structure until it exhausts the thread/process stack and crashes, causing a denial of service. No public exploit code was identified, but the attack requires only a crafted protocol message and no credentials.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 02, 2026

Stack-based buffer overflow in Apache LDAP API 1.2.0 through 1.2.8 allows unauthenticated remote attackers to crash server-side LDAP filter decoders by sending deeply nested search filters before the bind step, producing a denial-of-service condition. No public exploit code or CISA KEV listing was identified at time of analysis and no EPSS score was provided; the independently assessed CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, so the primary risk is remote availability loss rather than code execution.

RemediationAI

Upgrade to Apache Directory LDAP API 1.2.9, the vendor-released patch version that fixes the issue. If immediate upgrade is not possible, reduce exposure by restricting network access to LDAP services that use the vulnerable API so only trusted clients can submit search filters; this trade-off limits legitimate client access and may require compensating proxy or firewall rules. Where the application can be configured to reject filters before decoding or enforce a maximum filter nesting depth in a front-end parser, apply that as a temporary hardening measure, recognizing it may break complex legitimate LDAP queries. Because exploitation occurs before binding, authentication alone does not prevent the crash if the vulnerable decoder still processes pre-bind filter input. Monitor for crashes and review the vendor advisory at https://lists.apache.org/thread.html/fn3bwknn57266hx66w9vv6b4k8rfwcx7 for updates.

Affected VersionsENISA

Apache Directory LDAP API 1.2.0 <1.2.9

Affected Packages

euvd apache_directory_ldap_api fix: 1.2.9

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Apache Directory LDAP API is used by server-side LDAP components to parse and decode search filters supplied by clients. LDAP filters are recursively nested boolean expressions; a decoder that recurses without an effective depth limit can exhaust the call stack, and CWE-121 identifies this as a stack-based buffer overflow class. In CVE-2026-103552, a client can send a deeply nested search filter before binding, meaning the malicious input is processed in an unauthenticated pre-bind path, and overflow the server decoder stack. The CPE entry cpe:2.3:a:apache_software_foundation:apache_directory_ldap_api:*:*:*:*:*:*:*:* confirms the affected Apache Directory LDAP API library, while the description narrows the vulnerable range to 1.2.0 before 1.2.9. The assessed impact is availability only, consistent with a crash or denial of service rather than code execution or data compromise.

Know when Apache Directory Ldap Api gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (apache) PRIMARY 7.3 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
vuln.today AI 7.5 HIGH

Pre-bind network-reachable filter needs no auth (PR:N) and low complexity (AC:L); stack exhaustion yields a crash, so A:H with C:N/I:N.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Red Hat 7.5 HIGH

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Lifecycle Timeline

2
Patch available
Oct 02, 2026 - 11:17 EUVD
CVE Published
Oct 02, 2026 - 09:48 cve.org
CRITICAL

DescriptionCVE.org

Stack Overflow vulnerability in Apache Directory LDAP API.

Before binding, a client can send a deeply nested search filter that overflows the stack in the server's decoder.

This issue affects Apache Directory LDAP API: from 1.2.0 before 1.2.9.

Users are recommended to upgrade to version 1.2.9, which fixes the issue.

Executive ViewAI

Why It Matters

Apache LDAP API versions 1.2.0 through 1.2.8 are vulnerable to a stack-based buffer overflow that allows unauthenticated remote attackers to crash server-side LDAP filter decoders, causing a denial-of-service condition. No public exploit identified at time of analysis, but the flaw affects any application or service using these vulnerable library versions for LDAP authentication or directory lookups, potentially disrupting user access to critical systems. Leadership should prioritize remediation because the flaw requires no authentication and can be exploited remotely, leading to availability loss across dependent services.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include restricting network access to LDAP services to trusted sources, implementing rate limiting and deep packet inspection to detect and block deeply nested search filters, deploying WAF/IPS rules to drop malicious LDAP traffic, and monitoring for service crashes.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Medium
specialized Apache Java LDAP toolkit, common in Java LDAP stacks but not universal
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy