CVE-2026-14663: Cleartext Storage in a File or on Disk in PostgreSQL
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.
AI Analysis
Technical Summary
This vulnerability arises from the use of disabled ciphers in OpenSSL within PostgreSQL's pgcrypto functions (pgp_sym_encrypt, pgp_sym_decrypt, pgp_pub_encrypt, pgp_pub_decrypt, and their bytea variants). When these disabled ciphers are used, decryption can succeed even with an incorrect key, undermining the Modification Detection Code (MDC) protections and enabling recovery of cleartext from faulty ciphertext. The affected PostgreSQL versions are those prior to 18.5, 17.11, 16.15, 15.19, and 14.24.
Potential Impact
The vulnerability allows an attacker to recover cleartext data by direct observation of faulty ciphertext due to the failure of proper encryption protections. This compromises confidentiality and integrity of encrypted data processed by the affected pgcrypto functions. The impact is rated medium with a CVSS score of 6.5, indicating partial loss of confidentiality and integrity without availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should monitor PostgreSQL vendor advisories for updates and apply official fixes when available. Until a patch is released, avoid using affected pgcrypto functions with OpenSSL configurations that disable ciphers, or consider alternative encryption methods.
CVE-2026-14663: Cleartext Storage in a File or on Disk in PostgreSQL
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.
CVSS v3.1
Score 6.5medium
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability arises from the use of disabled ciphers in OpenSSL within PostgreSQL's pgcrypto functions (pgp_sym_encrypt, pgp_sym_decrypt, pgp_pub_encrypt, pgp_pub_decrypt, and their bytea variants). When these disabled ciphers are used, decryption can succeed even with an incorrect key, undermining the Modification Detection Code (MDC) protections and enabling recovery of cleartext from faulty ciphertext. The affected PostgreSQL versions are those prior to 18.5, 17.11, 16.15, 15.19, and 14.24.
Potential Impact
The vulnerability allows an attacker to recover cleartext data by direct observation of faulty ciphertext due to the failure of proper encryption protections. This compromises confidentiality and integrity of encrypted data processed by the affected pgcrypto functions. The impact is rated medium with a CVSS score of 6.5, indicating partial loss of confidentiality and integrity without availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should monitor PostgreSQL vendor advisories for updates and apply official fixes when available. Until a patch is released, avoid using affected pgcrypto functions with OpenSSL configurations that disable ciphers, or consider alternative encryption methods.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- PostgreSQL
- Date Reserved
- 2026-07-03T20:28:08.416Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7dc615bf8831d5393e527c
Added to database: 08/13/2026, 13:26:45 UTC
Last enriched: 08/13/2026, 14:02:03 UTC
Last updated: 08/13/2026, 15:57:29 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.