Cleartext Storage of Sensitive Information Affecting postgresql18 package, versions <0:18.6-0.1.hum1


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.1% (1st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-POSTGRESQL18-19506198
  • published3 Sept 2026
  • disclosed13 Aug 2026

Introduced: 13 Aug 2026

NewCVE-2026-14663  (opens in a new tab)
CWE-312  (opens in a new tab)

How to fix?

Upgrade RHEL:10 postgresql18 to version 0:18.6-0.1.hum1 or higher.
This issue was patched in RHSA-2026:54751.

NVD Description

Note: Versions mentioned in the description apply only to the upstream postgresql18 package and not the postgresql18 package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

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.6, 17.11, 16.15, 15.19, and 14.24 are affected.

CVSS Base Scores

version 3.1