CVE-2026-14940

MEDIUMNVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-07-07. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(high)
EPSS
21.2%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 9, 2026

Advisory Details (2)

Auto-updated Jul 7, 2026
Patch available. Sources: redhat.
redhat

2497697 – (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=2497697
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-14940

Vendor 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 18× in last 7d / 18× 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.

  1. 2026-07-13 06:12 UTCEPSS rescore
  2. 2026-07-12 21:07 UTCEG score recompute
  3. 2026-07-12 21:07 UTCGHSA enrichment
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 19:52 UTCEG score recompute
  6. 2026-07-11 19:52 UTCGHSA enrichment
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-10 18:38 UTCEG score recompute
  9. 2026-07-10 18:38 UTCGHSA enrichment
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 17:23 UTCEG score recompute
  12. 2026-07-09 17:23 UTCGHSA enrichment
  13. 2026-07-08 16:07 UTCEG score recompute
  14. 2026-07-08 16:07 UTCGHSA enrichment
  15. 2026-07-08 15:15 UTCEPSS rescore
  16. 2026-07-08 15:15 UTCEPSS rescore
  17. 2026-07-07 14:52 UTCEG score recompute
  18. 2026-07-07 14:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-14940?
CVE-2026-14940 is a medium vulnerability published on July 7, 2026. 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…
When was CVE-2026-14940 disclosed?
CVE-2026-14940 was first published in the National Vulnerability Database on July 7, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14940 actively exploited?
CVE-2026-14940 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-14940?
CVE-2026-14940 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-14940?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14940, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-14940

Explore →

Is Your Infrastructure Affected by CVE-2026-14940?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs