CVE-2026-14969: 389-ds-base: 389-ds-base: static initialization vector in aes-cbc/3des-cbc attribute encryption

Published Jul 7, 2026
·
Updated

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.

Other sources

A flaw was found in 389-ds-base. The LDBM backend attribute encryption implementation in ldap/servers/slapd/back-ldbm/ldbmattrcrypt.c uses a hardcoded static initialization vector (IV) — 16 bytes of 0x61 — for all AES-CBC-PAD and 3DES-CBC-PAD encryption operations. CBC mode requires a unique, unpredictable IV per encryption operation to provide semantic security. The static IV causes identical plaintext attribute values to produce identical ciphertext, enabling an attacker with privileged read access to the LDBM database files to detect plaintext equality across entries by comparing ciphertext blocks and to facilitate offline cryptanalysis of encrypted attributes.

Red Hat

Affected Software

9 affected components
389-ds-base=
redhat Directory Server=11.0
redhat Directory Server=12.0
redhat Directory Server=13.0
redhat 389 Directory Server
redhat Enterprise Linux=7.0
redhat Enterprise Linux=8.0
redhat Enterprise Linux=9.0
redhat Enterprise Linux=10.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Modify the LDBM backend attribute encryption code in ldap/servers/slapd/back-ldbm/ldbm_attrcrypt.c so AES-CBC-PAD and 3DES-CBC-PAD encryptions use a unique, unpredictable 16-byte IV for each encryption operation (replace the hardcoded 16-byte 0x61 static IV).

    389-ds-base (ldap/servers/slapd/back-ldbm/ldbm_attrcrypt.c LDBM backend attribute encryption) AES-CBC-PAD/3DES-CBC-PAD initialization vector (IV) generation = Use a unique, unpredictable IV per encryption operation instead of the hardcoded 16 bytes of 0x61

Event History

Jul 7, 2026
Data Sourced
via Red Hat·03:36 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·03:48 PM
Data Sourced
via MITRE·03:48 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-14969?

The severity of CVE-2026-14969 is rated as medium with a score of 4.4.

2

How do I fix CVE-2026-14969?

To fix CVE-2026-14969, update the 389-ds-base to a version that addresses this vulnerability.

3

What kind of access is required to exploit CVE-2026-14969?

An attacker needs privileged filesystem access to exploit CVE-2026-14969.

4

What impact does CVE-2026-14969 have on data security?

CVE-2026-14969 allows an attacker to detect plaintext equality across encrypted entries, compromising data confidentiality.

5

Which operations are affected by CVE-2026-14969?

CVE-2026-14969 affects AES-CBC and 3DES-CBC operations in the attribute encryption of 389-ds-base.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203