A heap-buffer-overflow flaw was found in 389 Directory Server (389-ds-base). When normalizing a Distinguished Name (DN) that contains a legacy-quoted value encoding a multivalued nested Relative Distinguished Name (RDN), the server can write past the end of a heap allocation while sorting RDN attribute-value pairs. An unauthenticated remote attacker can trigger this condition by sending an LDAP operation whose DN reaches the DN normalization routine, such as a search with a crafted base DN. This can corrupt heap memory and may cause denial of service.
CVE-2026-14940
Score 5.3 from GitHub Security Advisory published 2026-07-07. NVD baseline CVSS 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 21.5%
- KEV
- Not listed
Published
July 7, 2026
Last Modified
July 9, 2026
Advisory Details (2)
Auto-updated Jul 7, 20262497697 – (CVE-2026-14940) CVE-2026-14940 389-ds-base: 389-ds-base: heap-buffer-overflow in DN normalization via quoted multivalued RDN
https://bugzilla.redhat.com/show_bug.cgi?id=2497697Vendor Advisories for CVE-2026-14940(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 29× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 02:08 UTCGHSA enrichment
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 00:51 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 23:36 UTCGHSA enrichment
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 22:22 UTCGHSA enrichment
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-12 21:07 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 19:52 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 18:38 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 17:23 UTCGHSA enrichment
- 2026-07-08 16:07 UTCGHSA enrichment
Show 4 moreShow fewer
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 14:52 UTCEG score recompute
- 2026-07-07 14:52 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-14940?
When was CVE-2026-14940 disclosed?
Is CVE-2026-14940 actively exploited?
What is the CVSS score of CVE-2026-14940?
How do I remediate CVE-2026-14940?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-14940
Is Your Infrastructure Affected by CVE-2026-14940?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.