CVE-2026-86344

waiting for further signals

GHSA-62jf-8m49-534w ↗EUVD-2026-91076 ↗

no check availablenot proven exploitable

cve.orgpublic pockev

Red Hat Directory Server 11

CWE-400 Uncontrolled Resource Consumption

ETK-2026-282, permanent identifier

cvss7.5cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

19d 19h 13msince last run

55mAI analysis

timeline

0 = cve.org publication

trigger signal (cve.org) +0hwaiting for further signals+1h13m

+2h

+4h

+6h

+8h

+10h

+12h

description

Affected 389-ds-base deployments can have their LDAP worker pool exhausted by an unauthenticated remote client. The condition requires the attacker to maintain specially timed LDAP connections, after which LDAP service can be denied to other clients.

mitigation

Restrict LDAP network access to trusted hosts and networks while monitoring for long-lived or stalled client connections. No fixed version is recorded for the affected package streams; apply a vendor update when one becomes available.

check

exploit

automation

–

auth required

EPSS

0.35%26th percentile

agent run time

55m

cve.org record, t = 0

2026-10-01 21:29Z

Δ to public poc

–

Δ to kev

–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

2026-10-01 21:29Z
cve_org: trigger signal, started the run
https://www.cve.org/CVERecord?id=CVE-2026-86344

this entry in the feed

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

{
  "etk_id": "ETK-2026-282",
  "cve_id": "CVE-2026-86344",
  "display_id": "CVE-2026-86344",
  "ghsa_id": "GHSA-62jf-8m49-534w",
  "euvd_id": "EUVD-2026-91076",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated worker-pool exhaustion in 389-ds-base",
  "summary": "Affected 389-ds-base deployments can have their LDAP worker pool exhausted by an unauthenticated remote client. The condition requires the attacker to maintain specially timed LDAP connections, after which LDAP service can be denied to other clients.",
  "mitigation": "Restrict LDAP network access to trusted hosts and networks while monitoring for long-lived or stalled client connections. No fixed version is recorded for the affected package streams; apply a vendor update when one becomes available.",
  "vendor": "Red Hat",
  "product": "Red Hat Directory Server 11",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "389-ds-base",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "redhat-ds:11/389-ds-base",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "redhat-ds:12/389-ds-base",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "389-ds:1.4/389-ds-base",
      "purl": null
    }
  ],
  "cwes": [
    400
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0035,
  "epss_percentile": 0.2683,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 55.0046949,
  "t0_at": "2026-10-01T21:29:55.877000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T21:29:55.877000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T21:29:55.877000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-86344"
    }
  }
}

published 2026-10-01 21:47Z
last change 2026-10-21 17:00Z

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.