CVE-2026-11793: 389-ds-base: 389-ds-base: stack buffer overflow in checkprefix() algorithm id parsing
Noroxi assessment
Priority: Monitor (action score 19/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: 389-ds (openSUSE:Leap 16.0) 3.0.6~git382.7a51ea5f5-160000.1.1; 389-ds (openSUSE:Tumbleweed) 3.2.2+4b41542b2-1.1; 389-ds (SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS) 2.2.10~git255.752643c78-150500.3.48.1.
Low priority for now. Upgrade to 389-ds (openSUSE:Leap 16.0) 3.0.6~git382.7a51ea5f5-160000.1.1; 389-ds (openSUSE:Tumbleweed) 3.2.2+4b41542b2-1.1; 389-ds (SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS) 2.2.10~git255.752643c78-150500.3.48.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A stack buffer overflow flaw was found in 389 Directory Server. The checkPrefix() function in pw.c copies an attacker-controlled algorithm ID into a 256-byte stack buffer without bounds checking when parsing reversible-encrypted attribute values. An attacker with Directory Manager privileges can crash the LDAP server by storing a crafted credential with an oversized algorithm ID. FORTIFY_SOURCE mitigates this to denial of service only.
- Published
- Jun 9, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-121
Report tools
Action score
19
Low priority for now.
- CVSS
- 19 / 40 · 4.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · redhat
- 4.9
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redhat | 389 directory server | cpe:2.3:o:redhat:389_directory_server |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Red Hat Red Hat Directory Server 11
- all versionsaffected
Red Hat Red Hat Directory Server 12
- all versionsaffected
Red Hat Red Hat Directory Server 13
- all versionsaffected
Red Hat Red Hat Enterprise Linux 10
- all versionsaffected
Red Hat Red Hat Enterprise Linux 6
- all versionsunknown
Red Hat Red Hat Enterprise Linux 7
- all versionsaffected
Red Hat Red Hat Enterprise Linux 8
- all versionsaffected
Red Hat Red Hat Enterprise Linux 9
- all versionsaffected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat 389 directory serverall versions
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | 389-ds-base | from 0 | — |
| openSUSE:Leap 16.0 | 389-ds | before 3.0.6~git382.7a51ea5f5-160000.1.1 | 3.0.6~git382.7a51ea5f5-160000.1.1 |
| openSUSE:Tumbleweed | 389-ds | before 3.2.2+4b41542b2-1.1 | 3.2.2+4b41542b2-1.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | 389-ds | before 2.2.10~git255.752643c78-150500.3.48.1 | 2.2.10~git255.752643c78-150500.3.48.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP7 | 389-ds | before 2.7.0~git212.9b0755edb-150700.3.19.1 | 2.7.0~git212.9b0755edb-150700.3.19.1 |
| SUSE:Linux Enterprise Server 15 SP6-LTSS | 389-ds | before 2.2.10~git255.752643c78-150600.8.32.1 | 2.2.10~git255.752643c78-150600.8.32.1 |
| SUSE:Linux Enterprise Server 16.0 | 389-ds | before 3.0.6~git382.7a51ea5f5-160000.1.1 | 3.0.6~git382.7a51ea5f5-160000.1.1 |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-1949An access control bypass vulnerability found in 389-ds-base.30Monitor
- CVE-2018-10935A flaw was found in the 389 Directory Server that allows users to cause a crash in the LDAP server using ldapsearch with server side sort.27Monitor
- CVE-2022-0996A vulnerability was found in the 389 Directory Server that allows expired passwords to access the database to cause improper authentication.26Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-35518Mar 26, 2021 · When binding against a DN during authentication, the reply from 389-ds-base will be different whether the DN exists or not.21Monitor
- ← EarlierCVE-2021-3514May 28, 2021 · When using a sync_repl client in 389-ds-base, an authenticated attacker can cause a NULL pointer dereference using a specially crafted…26Monitor
- ← EarlierCVE-2024-1062Feb 12, 2024 · 389-ds-base: a heap overflow leading to denail-of-servce while writing a value larger than 256 chars (in log_entry_attr)22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:389-ds | 3.2.2+4b41542b2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:389-ds | 3.0.6~git382.7a51ea5f5-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-121 · Stack-based Buffer OverflowCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.