CVE-2026-103880

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Asymmetric Resource Consumption vulnerability in Apache Directory LDAP API.

Storing a password using the bcrypt algorithm with a high force like 30 in a LDAP server that supports this algorithm will cause the server CPU to  run for hours checking the credentials. A bounded cost should be enforced to avoid a server DOS.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

Published

October 2, 2026

Last Modified

October 2, 2026

Vendor Advisories for CVE-2026-103880(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
apache-directory-api2.1.2-1, 2.1.2-2
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
apache-directory-api2.1.2-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
apache-directory-api2.1.2-2
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 23:21 UTCEPSS rescore
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-02 22:21 UTCGHSA enrichment
  4. 2026-10-02 22:20 UTCNVD update
  5. 2026-10-02 21:24 UTCGHSA enrichment
  6. 2026-10-02 21:20 UTCMITRE cvelistV5
  7. 2026-10-02 14:42 UTCGHSA enrichment
  8. 2026-10-02 10:18 UTCNVD update
  9. 2026-10-02 10:16 UTCEG score recompute
  10. 2026-10-02 10:15 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-103880?
CVE-2026-103880 is a publicly disclosed vulnerability published on October 2, 2026. Asymmetric Resource Consumption vulnerability in Apache Directory LDAP API. Storing a password using the bcrypt algorithm with a high force like 30 in a LDAP server that supports this algorithm will cause the server CPU to run for hours checking the credentials. A bounded cost should be enforced to…
When was CVE-2026-103880 disclosed?
CVE-2026-103880 was first published on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-103880 actively exploited?
CVE-2026-103880 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-103880?
A fix for CVE-2026-103880 is available — its CVE record says: "Users are recommended to upgrade to version 2.1.9, which fixes the issue." The vendor advisories EchelonGraph has for CVE-2026-103880 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-103880

Explore →

Is Your Infrastructure Affected by CVE-2026-103880?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.