cve.bz

CVE-2026-103885 apache software foundation apache directory ldap api: Uncontrolled Resource Consumption

7.5 highEPSS 0.4%

High (7.5) in apache software foundation apache directory ldap api. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Asymmetric Resource Consumption vulnerability in Apache Directory LDAP API. A LDAP server using the LDAP API (like Apache DS) may consume 100% of a CPU core indefinitely when processing some badly crafted Telephone Numbers. This issue affects Apache Directory LDAP API: from 2.1.0 before 2.1.9. Users are recommended to upgrade to version 2.1.9, which fixes the issue.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-103885 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103885?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103885?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-103885 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • apache software foundation:apache directory ldap api

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Directory LDAP APIfrom 2.1.0 before 2.1.9

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13apache-directory-apino fix listedDEBIAN-CVE-2026-103885
Debian14apache-directory-api2.1.9-1DEBIAN-CVE-2026-103885
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 moreapache-directory-apino fix listedUBUNTU-CVE-2026-103885

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important because an unauthenticated remote attacker can completely consume host CPU capacity without requiring privileges or user interaction, resulting in a denial of service. The issue is triggered when an application using the LDAP API processes invalid or malformed telephone number attributes. Red Hat products are not affected because they do not ship the vulnerable 2.1.x codebase, relying instead on earlier generation releases where the flawed parsing logic is absent.

ProductPackageStateAdvisory
Red Hat Fuse 7api-ldap-modelNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-103885.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON