PostgreSQL up to 17.10/18.4 GSSAPI message integrity

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.
6.0$0-$5k0.52

Summaryinfo

A vulnerability was found in PostgreSQL up to 17.10/18.4 and classified as critical. The affected element is an unknown function of the component GSSAPI. Executing a manipulation can lead to message integrity. This vulnerability appears as CVE-2026-14681. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability was found in PostgreSQL up to 17.10/18.4. It has been declared as critical. This vulnerability affects an unknown code of the component GSSAPI. The manipulation with an unknown input leads to a message integrity vulnerability. The CWE definition for the vulnerability is CWE-924. The product establishes a communication channel with an endpoint and receives a message from that endpoint, but it does not sufficiently ensure that the message was not modified during transmission. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Improper enforcement of message integrity in PostgreSQL GSSAPI support allows a user to negotiate GSSAPI contrary to pg_hba.conf rules, via initial direct TLS connection. Despite a pg_hba.conf that appears to require GSSAPI, the connection may exchange data over TLS encryption alone. If the TLS settings are more permissive than the GSS settings, the connection may continue with lesser protection. Within major versions 17-18, minor versions before PostgreSQL 18.5 and 17.11 are affected. Versions before PostgreSQL 17 are unaffected.

The advisory is shared for download at postgresql.org. This vulnerability was named CVE-2026-14681 since 07/03/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available.

Upgrading to version 17.11 or 18.5 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 6.0

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Message integrity
CWE: CWE-924 / CWE-354 / CWE-345
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: PostgreSQL 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/13/2026 +0 days VulDB entry last update

Sourcesinfo

Product: postgresql.org

Advisory: postgresql.org
Status: Confirmed

CVE: CVE-2026-14681 (🔒)
GCVE (CVE): GCVE-0-2026-14681
GCVE (VulDB): GCVE-100-389428

Entryinfo

Created: 08/13/2026 15:44
Changes: 08/13/2026 15:44 (54)
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 want to use VulDB in your project?

Use the official API to access entries easily!