Skip to content
VulniPulse
Critical 2 vendors · 2 advisories

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

CVE-2026-14663 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Critical
CVSS base score
6.5 (Red Hat)
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N · base score 6.5, scored by PostgreSQLAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: low. Integrity impact: low. Availability impact: none.
Weakness
  • CWE-313 Cleartext Storage in a File or on Disk
  • CWE-345 Insufficient Verification of Data Authenticity
EPSS
0.11% chance of exploitation in the next 30 days (1st percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
Fixed releases
  • Red Hat: postgresql18-main-18.6-0.1.hum1, postgresql17-main-17.11-1.hum1, RHSA-2026:54751, RHSA-2026:57198
Vendor advisories
2 from Red Hat, Splunk
Assigned by
PostgreSQL (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-14663; each belongs to its advisory, not to every product listed. How records are collected and checked.

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

Text from the CVE.org record (PostgreSQL).

How do I fix CVE-2026-14663?

Upgrade to a fixed release named by the vendor:

  • Red Hat: postgresql18-main-18.6-0.1.hum1, postgresql17-main-17.11-1.hum1, RHSA-2026:54751, RHSA-2026:57198
  • To mitigate this vulnerability, administrators should avoid using pgcrypto encryption and decryption operations with ciphers that are disabled by the system's OpenSSL configuration or local security policies. Organizations should proactively review their OpenSSL cipher policies to ensure required cryptographic algorithms are fully supported, or transition to robust, enabled algorithms within pgcrypto. Additionally, applications should treat all encrypted input as untrusted and independently validate data (Red Hat)
  • Workaround: Use FIPS-compliant ciphers or other OpenSSL-enabled ciphers (CVE.org record)

Vendor advisories for CVE-2026-14663

Red Hat

1 advisory
  • Advisory severityMedium6.5

    Medium [CVE-2026-14663] PostgreSQL pgcrypto: Information disclosure via cleartext storage with disabled ciphers

    CVE-2026-14663Source published Source 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 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. This is a Moderate impact flaw in PostgreSQL's pgcrypto module where disabled ciphers can lead to information disclosure. This vulnerability primarily affects instances utilizing the pgcrypto module for…

    Affected products in this advisory
    • Red Hat Hardened Images
    • Red Hat Enterprise Linux 10
    • Red Hat Enterprise Linux 6
    • Red Hat Enterprise Linux 7

    5 more entries in the full advisory.

    Source-reported affected versions
    • < 18.5
    • < 17.11
    • < 16.15
    • < 15.19

    1 more entries in the full advisory.

    Source-reported fixed versions
    • postgresql18-main-18.6-0.1.hum1
    • postgresql17-main-17.11-1.hum1
    • RHSA-2026:54751
    • RHSA-2026:57198
    Mitigation guidance
    • To mitigate this vulnerability, administrators should avoid using pgcrypto encryption and decryption operations with ciphers that are disabled by the system's OpenSSL configuration or local security policies. Organizations should proactively review their OpenSSL cipher policies to ensure required cryptographic algorithms are fully supported, or transition to robust, enabled algorithms within pgcrypto. Additionally, applications should treat all encrypted input as untrusted and independently validate data

Splunk

1 advisory
  • Advisory severityCritical

    Critical [CVE-2025-61726 +79] Third-Party Package Updates in Splunk Enterprise - November 2026

    SVD-2026-1104Source published

    This bulletin covers 80 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.

    Splunk remedied common vulnerabilities and exposures (CVEs) in third-party packages in Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher. Affected products named by the advisory: Splunk Enterprise 10.6; Splunk Enterprise 10.4; Splunk Enterprise 10.2; Splunk Enterprise 10.0; and 1 more. Affected products named by the advisory: Splunk Enterprise 9.4.

    Affected products in this advisory
    • Splunk Enterprise 10.6
    • Splunk Enterprise 10.4
    • Splunk Enterprise 10.2
    • Splunk Enterprise 10.0

    1 more entries in the full advisory.

    Source-reported affected versions
    • Splunk Enterprise 10.6.0.5
    • Splunk Enterprise 10.4.0 to 10.4.4
    • Splunk Enterprise 10.2.0 to 10.2.8
    • Splunk Enterprise 10.0.0 to 10.0.11

    1 more entries in the full advisory.

    Source-reported fixed versions
    • Splunk Enterprise 10.6.1
    • Splunk Enterprise 10.4.5
    • Splunk Enterprise 10.2.9
    • Splunk Enterprise 10.0.12

    1 more entries in the full advisory.

    Mitigation guidance
    • Upgrade Splunk Enterprise to an applicable fixed release identified in the OSS entries below. The listed versions contain different component updates; the details specify which releases contain each fix.

References

Timeline

  1. CVE record published
  2. CVE record last updated
  3. First vendor advisory listed by VulniPulse

All Red Hat advisories

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Red Hat