CVE-2026-14663: PostgreSQL pgcrypto, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext

Published Aug 13, 2026
·
Updated

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 pgpsymencrypt, pgpsymdecrypt, pgppubencrypt, pgppubdecrypt, pgpsymencryptbytea, pgpsymdecryptbytea, pgppubencryptbytea, and pgppubdecryptbytea. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

Other sources

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

Microsoft

Affected Software

11 affected componentsFixes available
PostgreSQL pgcrypto><18.5
PostgreSQL pgcrypto><17.11
PostgreSQL pgcrypto><16.15
PostgreSQL pgcrypto><15.19
PostgreSQL pgcrypto><14.24
PostgreSQL postgresql>=14.0<14.24
PostgreSQL postgresql>=15.0<15.19
PostgreSQL postgresql>=16.0<16.15
PostgreSQL postgresql>=17.0<17.11
PostgreSQL postgresql>=18.0<18.5
Microsoft azl3 postgresql 16.14-1<16.15-1
16.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.15-1
  2. Upgrade

    Upgrade PostgreSQL pgcrypto to a version that resolves this vulnerability.

    Fixed in 18.6
  3. Upgrade

    Upgrade PostgreSQL pgcrypto to a version that resolves this vulnerability.

    Fixed in 17.11
  4. Upgrade

    Upgrade PostgreSQL pgcrypto to a version that resolves this vulnerability.

    Fixed in 16.15
  5. Upgrade

    Upgrade PostgreSQL pgcrypto to a version that resolves this vulnerability.

    Fixed in 15.19
  6. Upgrade

    Upgrade PostgreSQL pgcrypto to a version that resolves this vulnerability.

    Fixed in 14.24

Event History

Aug 13, 2026
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:17 PM
DescriptionSeverityWeaknessAffected Software
Aug 15, 2026
Data Sourced
via Microsoft·02:28 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·02:28 AM
Affected Software
Updated
via Microsoft·02:28 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2026-14663?

The severity of CVE-2026-14663 is medium with a CVSS score of 6.5.

2

How do I fix CVE-2026-14663?

To fix CVE-2026-14663, update PostgreSQL pgcrypto to a version that addresses the issue with OpenSSL-disabled ciphers.

3

What does CVE-2026-14663 affect?

CVE-2026-14663 affects the PostgreSQL pgcrypto extension, specifically regarding its handling of OpenSSL-disabled ciphers.

4

What are the risks associated with CVE-2026-14663?

The risks associated with CVE-2026-14663 include the potential for sensitive data to be exposed due to the recovery of cleartext from faulty ciphertext.

5

Can CVE-2026-14663 lead to unauthorized data access?

Yes, CVE-2026-14663 can lead to unauthorized data access if encrypted data is processed without appropriate validation.

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