CVE-2026-14663 PUBLISHED

PostgreSQL pgcrypto, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext

Assigner: PostgreSQL
Reserved: 03.07.2026 Published: 13.08.2026 Updated: 13.08.2026

Cleartext storage in PostgreSQL pgcrypto disabled ciphers allows a user to recover cleartext, via direct observation of the faulty ciphertext. The OpenSSL version and OpenSSL configuration determine the disabled ciphers. If the application accepts encrypted data as input, decryption will succeed even with the wrong key. This in turn loses the modest protection from the Modification Detection Code (MDC). Affected functions are pgp_sym_encrypt, pgp_sym_decrypt, pgp_pub_encrypt, pgp_pub_decrypt, pgp_sym_encrypt_bytea, pgp_sym_decrypt_bytea, pgp_pub_encrypt_bytea, and pgp_pub_decrypt_bytea. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CVSS Score: 6.5

Product Status

Vendor n/a
Product PostgreSQL
Versions Default: unaffected
  • affected from 18 to 18.5 (excl.)
  • affected from 17 to 17.11 (excl.)
  • affected from 16 to 16.15 (excl.)
  • affected from 15 to 15.19 (excl.)
  • affected from 0 to 14.24 (excl.)

Affected Configurations

A data owner is managing encrypted data with the pgcrypto extension.

Workarounds

Use FIPS-compliant ciphers or other OpenSSL-enabled ciphers

Credits

  • The PostgreSQL project thanks Shishir Sharma for reporting this problem.

References

Problem Types

  • Cleartext Storage in a File or on Disk CWE
  • Insufficient Verification of Data Authenticity CWE