Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Workaround
Use FIPS-compliant ciphers or other OpenSSL-enabled ciphers
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-6438-1 | postgresql-17 security update |
| Link | Providers |
|---|---|
| https://www.postgresql.org/support/security/CVE-2026-14663/ |
|
Thu, 13 Aug 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 13 Aug 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Postgresql
Postgresql postgresql |
|
| Vendors & Products |
Postgresql
Postgresql postgresql |
Thu, 13 Aug 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | PostgreSQL pgcrypto, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext | |
| Weaknesses | CWE-313 CWE-345 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: PostgreSQL
Published:
Updated: 2026-08-13T15:34:25.917Z
Reserved: 2026-07-03T20:28:08.416Z
Link: CVE-2026-14663
Updated: 2026-08-13T15:19:58.692Z
Status : Received
Published: 2026-08-13T13:17:43.700
Modified: 2026-08-13T16:17:55.600
Link: CVE-2026-14663
No data.
OpenCVE Enrichment
Updated: 2026-08-13T15:15:12Z
Debian DSA