CVE-2026-11785 json
389-ds-base: 389-ds-base: partial stack address information leak via ber_printf type confusion in sso token handler
published 5mo ago modified 4d ago also EUVD-2026-35418
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
A flaw was found in 389 Directory Server. A type confusion in the SSO token extended operation handler causes partial stack address information to be disclosed in LDAP responses to authenticated users.
Patch / fix
- 389-ds SLES for SAP applications 16.0, SLES 16.0 3.0.6~git382.7a51ea5f5-160000.1.1
- 389-ds SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS +1 more 2.2.10~git272.fd28f95da-150500.3.51.1
- 389-ds SLE Module for Server Applications 15 SP7 2.7.0~git234.0afa2e38b-150700.3.22.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~git272.fd28f95da-150600.8.35.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:3687-1SUSE-SU-2026:3686-1SUSE-SU-2026:3678-1SUSE-SU-2026:3138-1SUSE-SU-2026:3137-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
Is CVE-2026-11785 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor 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-11785 updated cvss 4.3
389-ds-base: 389-ds-base: partial stack address information leak via ber_printf type confusion in SSO token handler
-
Red Hat Directory Server 12 389-ds-base 2.6.1-3.module+el9dsrv+23022+962c3fa5 Red Hat Directory Server 13 389-ds-base 3.0.6-2.el10dsrv Red Hat Enterprise Linux 9 389-ds-base, python3-lib389, 389-ds-base-libs, 389-ds-base-snmp, 389-ds-base 3.0.6-2.el10dsrv Red Hat Enterprise Linux 10 389-ds-base 3.0.6-2.el10dsrvaffected: workaround, no fix available “Fix deferred”
-
Red Hat Directory Server 11 389-ds-base 1.4.3.34-14.module+el8dsrv+24041+386df666 Red Hat Enterprise Linux 6 389-ds-base, 389-ds-base-libs, 389-ds-base 3.0.6-2.el10dsrv Red Hat Enterprise Linux 7 389-ds-base, 389-ds-base-libs, 389-ds-base-snmp, 389-ds-base 3.0.6-2.el10dsrv 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, +1 morenot affected: vulnerable code not present
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
- 5mo ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
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-843 Access of Resource Using Incompatible Type
References
-
access.redhat.com
/security/cve/CVE-2026-11785
vdb-entry, vendor-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=2485427
issue-tracking, vendor-advisory
Sources
- CVE List CVE-2026-11785
- NVD CVE-2026-11785
Fencer Intel 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.