PostgreSQL up to 18.4 pgcrypto cleartext storage

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, was found in PostgreSQL up to 14.23/15.18/16.14/17.10/18.4. Affected by this issue is the function pgp_sym_encrypt/pgp_sym_decrypt/pgp_pub_encrypt/pgp_pub_decrypt/pgp_sym_encrypt_bytea/pgp_sym_decrypt_bytea/pgp_pub_encrypt_bytea/pgp_pub_decrypt_bytea of the component pgcrypto. The manipulation results in cleartext storage. This vulnerability is reported as CVE-2026-14663. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability classified as problematic has been found in PostgreSQL up to 14.23/15.18/16.14/17.10/18.4. Affected is the function pgp_sym_encrypt/pgp_sym_decrypt/pgp_pub_encrypt/pgp_pub_decrypt/pgp_sym_encrypt_bytea/pgp_sym_decrypt_bytea/pgp_pub_encrypt_bytea/pgp_pub_decrypt_bytea of the component pgcrypto. The manipulation with an unknown input leads to a cleartext storage vulnerability. CWE is classifying the issue as CWE-312. The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. This is going to have an impact on confidentiality. CVE summarizes:

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.

The advisory is shared for download at postgresql.org. This vulnerability is traded as CVE-2026-14663 since 07/03/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1555.

The vulnerability scanner Nessus provides a plugin with the ID 341035 (SUSE SLES12: postgresql16 / postgresql16-contrib / postgresql16-devel / etc (SUSE-SU-2026:3794-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 14.24, 15.19, 16.15, 17.11 or 18.5 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (341035) and CERT Bund (WID-SEC-2026-2844). Once again VulDB remains the best source for vulnerability data.

Affected

  • Open Source PostgreSQL

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.3

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 6.5
CNA Vector (PostgreSQL): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Cleartext storage
CWE: CWE-312 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 341035
Nessus Name: SUSE SLES12: postgresql16 / postgresql16-contrib / postgresql16-devel / etc (SUSE-SU-2026:3794-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: PostgreSQL 14.24/15.19/16.15/17.11/18.5

Timelineinfo

07/03/2026 CVE reserved
08/13/2026 +41 days Advisory disclosed
08/13/2026 +0 days VulDB entry created
08/31/2026 +17 days VulDB entry last update

Sourcesinfo

Product: postgresql.org

Advisory: postgresql.org
Status: Confirmed

CVE: CVE-2026-14663 (🔒)
GCVE (CVE): GCVE-0-2026-14663
GCVE (VulDB): GCVE-100-389412
CERT Bund: WID-SEC-2026-2844 - PostgreSQL: Mehrere Schwachstellen

Entryinfo

Created: 08/13/2026 15:35
Updated: 08/31/2026 01:23
Changes: 08/13/2026 15:35 (55), 08/16/2026 00:44 (7), 08/27/2026 16:02 (2), 08/31/2026 01:23 (12)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!