Skip to content
Fencer Vulns
medium 6.5

CVE-2026-11884 json

389-ds-base: 389-ds-base: heap buffer overflow in schema objectclass serialization due to missing oc_superior in size calculation

published 2026-06-10 4 mo ago modified 2026-11-05 4 d ago also EUVD-2026-36045

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

A heap buffer overflow flaw was found in 389 Directory Server. When serializing objectclass definitions, the oc_superior (SUP) field length is omitted from buffer size calculations in read_schema_dse() and schema_oc_to_string(), but the field is still written via strcat(). An attacker with Directory Manager privileges, or a compromised replication supplier, can trigger a server crash by creating objectclasses with long SUP values. This is an incomplete fix variant of CVE-2025-14905.

Patch / fix

  • 389-ds SLES for SAP applications 16.0, SLES 16.0 3.0.6~git382.7a51ea5f5-160000.1.1
  • 389-ds SLE Module for Server Applications 15 SP7 2.7.0~git212.9b0755edb-150700.3.19.1
  • 389-ds SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS +1 more 2.2.10~git255.752643c78-150500.3.48.1
  • 389-ds SLES for SAP 15 SP6, SLES 15 SP6-LTSS 2.2.10~git255.752643c78-150600.8.32.1

suse advisories SUSE-SU-2026:23574-1SUSE-SU-2026:3138-1SUSE-SU-2026:3137-1SUSE-SU-2026:3136-1

  • 389-ds openSUSE Leap 16.0 3.0.6~git382.7a51ea5f5-160000.1.1
  • 389-ds openSUSE Tumbleweed 3.2.2+4b41542b2-1.1

opensuse advisories openSUSE-SU-2026:21691-1openSUSE-SU-2026:11600-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-11884 updated cvss 6.5

389-ds-base: 389-ds-base: heap buffer overflow in schema objectclass serialization due to missing oc_superior in size calculation

  • Red Hat Directory Server 11 389-ds-base Red Hat Directory Server 12 389-ds-base Red Hat Directory Server 13 389-ds-base
    affected: workaround, no fix available “Restrict Directory Manager access. Audit replication agreements. Monitor cn=schema modifications for unusually long SUP values. Restrict LDAP replication traffic to trusted networks.”
  • Red Hat Enterprise Linux 6 389-ds-base, 389-ds-base-libs
    affected: workaround, no fix planned “Restrict Directory Manager access. Audit replication agreements. Monitor cn=schema modifications for unusually long SUP values. Restrict LDAP replication traffic to trusted networks.”
  • Red Hat Enterprise Linux 7 389-ds-base, 389-ds-base-libs, 389-ds-base-snmp Red Hat Enterprise Linux 8 389-ds-base, cockpit-389-ds, python3-lib389, 389-ds-base-libs, 389-ds-base-snmp, 389-ds-base-legacy-tools Red Hat Enterprise Linux 9 389-ds-base, python3-lib389, 389-ds-base-libs, 389-ds-base-snmp Red Hat Enterprise Linux 10 389-ds-base
    affected: workaround, no fix available “Restrict Directory Manager access. Audit replication agreements. Monitor cn=schema modifications for unusually long SUP values. Restrict LDAP replication traffic to trusted networks.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
4 mo ago

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H

Affected products

  • Red Hat Red Hat Directory Server 11
  • Red Hat Red Hat Directory Server 12
  • Red Hat Red Hat Directory Server 13
  • Red Hat Red Hat Enterprise Linux 10
  • Red Hat Red Hat Enterprise Linux 6
  • Red Hat Red Hat Enterprise Linux 7
  • Red Hat Red Hat Enterprise Linux 8
  • Red Hat Red Hat Enterprise Linux 9

Classification

Weakness
  • CWE-122 Heap-based Buffer Overflow

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.