CVE-2026-14969

MEDIUMNVD 4.44.4—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.4Exploit: None knownExposed services: Not assessed

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

A flaw was found in 389-ds-base where the LDBM backend attribute encryption uses a hardcoded static initialization vector for AES-CBC and 3DES-CBC operations, allowing an attacker with privileged filesystem access to detect plaintext equality across encrypted entries by comparing ciphertext blocks.

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

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 computed
Severity44% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

Published

July 7, 2026

Last Modified

July 9, 2026

Advisory Details (2)

Auto-updated Jul 7, 2026
No fix on record yet. Sources: redhat.
redhat

2497735 – (CVE-2026-14969) CVE-2026-14969 389-ds-base: 389-ds-base: Static initialization vector in AES-CBC/3DES-CBC attribute encryption

https://bugzilla.redhat.com/show_bug.cgi?id=2497735
redhatMentions a patch (unverified)

cve-details

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

Vendor Advisories for CVE-2026-14969(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
389-ds-base1.4.4.11-2 ... 3.1.2+vendor1-2 (23 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
389-ds-base2.3.1+dfsg1-1 ... 3.3.1-3 (18 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
389-ds-base3.1.2+dfsg1-1 ... 3.3.1-3 (8 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× 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.

Showing the most recent 100 of 133 total refreshes for this CVE.

  1. 2026-10-09 20:06 UTCEPSS rescore
  2. 2026-10-08 17:11 UTCEPSS rescore
  3. 2026-10-07 23:47 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-05 17:42 UTCEPSS rescore
  6. 2026-10-04 23:21 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:49 UTCEPSS rescore
  9. 2026-09-30 15:02 UTCEPSS rescore
  10. 2026-09-29 15:20 UTCEPSS rescore
  11. 2026-09-28 13:37 UTCEG score recompute
  12. 2026-09-28 13:37 UTCGHSA enrichment
  13. 2026-09-27 13:47 UTCEPSS rescore
  14. 2026-09-26 15:58 UTCEPSS rescore
  15. 2026-09-23 06:17 UTCEG score recompute
  16. 2026-09-23 06:17 UTCGHSA enrichment
  17. 2026-09-18 19:27 UTCEPSS rescore
  18. 2026-09-18 05:50 UTCEG score recompute
  19. 2026-09-18 05:50 UTCGHSA enrichment
  20. 2026-09-16 14:07 UTCEPSS rescore
  21. 2026-09-14 07:23 UTCEG score recompute
  22. 2026-09-14 07:23 UTCGHSA enrichment
  23. 2026-09-13 16:46 UTCEPSS rescore
  24. 2026-09-13 08:32 UTCGHSA enrichment
  25. 2026-09-12 03:43 UTCEG score recompute
Show 75 more
  1. 2026-09-12 03:43 UTCGHSA enrichment
  2. 2026-09-11 14:52 UTCEPSS rescore
  3. 2026-09-11 09:36 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-05 22:54 UTCEG score recompute
  9. 2026-09-05 22:54 UTCGHSA enrichment
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:11 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-08-30 07:43 UTCEG score recompute
  14. 2026-08-30 07:43 UTCGHSA enrichment
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 21:55 UTCEG score recompute
  18. 2026-08-27 21:55 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-26 13:00 UTCEG score recompute
  22. 2026-08-26 13:00 UTCGHSA enrichment
  23. 2026-08-25 13:48 UTCEPSS rescore
  24. 2026-08-25 02:59 UTCEG score recompute
  25. 2026-08-25 02:59 UTCGHSA enrichment
  26. 2026-08-24 04:09 UTCGHSA enrichment
  27. 2026-08-23 05:20 UTCEG score recompute
  28. 2026-08-23 05:20 UTCGHSA enrichment
  29. 2026-08-23 00:19 UTCEPSS rescore
  30. 2026-08-22 06:25 UTCGHSA enrichment
  31. 2026-08-21 07:27 UTCGHSA enrichment
  32. 2026-08-20 08:38 UTCEG score recompute
  33. 2026-08-20 08:38 UTCGHSA enrichment
  34. 2026-08-19 17:03 UTCEPSS rescore
  35. 2026-08-19 09:48 UTCGHSA enrichment
  36. 2026-08-18 10:55 UTCGHSA enrichment
  37. 2026-08-17 10:04 UTCGHSA enrichment
  38. 2026-08-16 11:15 UTCEG score recompute
  39. 2026-08-16 11:15 UTCGHSA enrichment
  40. 2026-08-16 02:14 UTCEPSS rescore
  41. 2026-08-15 12:27 UTCGHSA enrichment
  42. 2026-08-14 13:37 UTCEG score recompute
  43. 2026-08-14 13:37 UTCGHSA enrichment
  44. 2026-08-13 22:00 UTCEPSS rescore
  45. 2026-08-13 14:48 UTCGHSA enrichment
  46. 2026-08-12 15:59 UTCGHSA enrichment
  47. 2026-08-11 17:10 UTCEG score recompute
  48. 2026-08-11 17:10 UTCGHSA enrichment
  49. 2026-08-11 00:00 UTCEPSS rescore
  50. 2026-08-10 18:21 UTCGHSA enrichment
  51. 2026-08-09 19:32 UTCGHSA enrichment
  52. 2026-08-08 20:43 UTCEG score recompute
  53. 2026-08-08 20:43 UTCGHSA enrichment
  54. 2026-08-08 16:37 UTCEPSS rescore
  55. 2026-08-07 21:53 UTCEG score recompute
  56. 2026-08-07 21:53 UTCGHSA enrichment
  57. 2026-08-06 23:05 UTCEG score recompute
  58. 2026-08-06 23:04 UTCGHSA enrichment
  59. 2026-08-06 13:46 UTCEPSS rescore
  60. 2026-08-06 00:16 UTCEG score recompute
  61. 2026-08-06 00:15 UTCGHSA enrichment
  62. 2026-08-05 19:17 UTCEPSS rescore
  63. 2026-08-05 01:26 UTCEG score recompute
  64. 2026-08-05 01:26 UTCGHSA enrichment
  65. 2026-08-04 15:09 UTCEPSS rescore
  66. 2026-08-04 10:38 UTCEPSS rescore
  67. 2026-08-04 02:34 UTCGHSA enrichment
  68. 2026-08-03 03:45 UTCGHSA enrichment
  69. 2026-08-02 04:56 UTCGHSA enrichment
  70. 2026-08-01 06:07 UTCGHSA enrichment
  71. 2026-07-31 07:17 UTCEG score recompute
  72. 2026-07-31 07:16 UTCGHSA enrichment
  73. 2026-07-30 16:27 UTCEPSS rescore
  74. 2026-07-30 08:25 UTCEG score recompute
  75. 2026-07-30 08:25 UTCGHSA enrichment

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-14969?
CVE-2026-14969 is a medium vulnerability published on July 7, 2026. A flaw was found in 389-ds-base where the LDBM backend attribute encryption uses a hardcoded static initialization vector for AES-CBC and 3DES-CBC operations, allowing an attacker with privileged filesystem access to detect plaintext equality across encrypted entries by comparing ciphertext blocks.
When was CVE-2026-14969 disclosed?
CVE-2026-14969 was first published 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-14969 actively exploited?
CVE-2026-14969 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-14969?
CVE-2026-14969 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2026-14969?
No fix for CVE-2026-14969 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-14969 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-14969

Explore →

Is Your Infrastructure Affected by CVE-2026-14969?

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

Book a Demo →Browse All CVEs