CVE-2026-103885

waiting for further signalsZero needs more public information before it can validate it.

GHSA-c2cq-mmh3-7wxh ↗EUVD-2026-91362 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Apache Software Foundation Apache Directory LDAP API >= 2.1.0, < 2.1.9
fixed in 2.1.9
ETK-2026-578, permanent identifier
16d 09h 59msince last run
22mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+56h41m
0
+2h
+4h
+6h
+8h
+10h

description

Apache Directory LDAP API versions 2.1.0 through 2.1.8 can cause LDAP servers using the library to consume a CPU core indefinitely. An attacker must be able to submit specially malformed telephone-number values for the server to process.

mitigation

Upgrade org.apache.directory.api:api-ldap-model to version 2.1.9 or later. Prioritize the update on LDAP servers that accept untrusted directory requests.

fixed in 2.1.9

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.49%40th percentile
agent run time
22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 10:09Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-02 10:09Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-103885

{
  "etk_id": "ETK-2026-578",
  "cve_id": "CVE-2026-103885",
  "display_id": "CVE-2026-103885",
  "ghsa_id": "GHSA-c2cq-mmh3-7wxh",
  "euvd_id": "EUVD-2026-91362",
  "status": "published",
  "anchor_state": "anchored",
  "title": "CPU denial of service in Apache Directory LDAP API",
  "summary": "Apache Directory LDAP API versions 2.1.0 through 2.1.8 can cause LDAP servers using the library to consume a CPU core indefinitely. An attacker must be able to submit specially malformed telephone-number values for the server to process.",
  "mitigation": "Upgrade org.apache.directory.api:api-ldap-model to version 2.1.9 or later. Prioritize the update on LDAP servers that accept untrusted directory requests.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Directory LDAP API",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.1.0, < 2.1.9"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.1.9"
      ],
      "package_name": "org.apache.directory.api:api-ldap-model",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0049,
  "epss_percentile": 0.4074,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 21.738194066666665,
  "t0_at": "2026-10-02T10:09:51.901000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T10:09:51.901000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T10:09:51.901000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103885"
    }
  }
}

published 2026-10-04 18:29Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.