Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-14681: Improper enforcement of message integrity in PostgreSQL GSSAPI support allows a user to negotiate GSSAPI contr

15
Routine
MEDIUM 4.2UPGRADE

CVE-2026-14681 is a medium-severity flaw (CVSS 4.2) affecting postgresql. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 bef

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score4.2 (Medium)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededLow
User interactionNone
EPSS exploit chance0.1% (top 100%)
CISA exploited listNo
WeaknessCWE-924
Published2026-08-13
Last modified2026-08-29
Publisher (CNA): PostgreSQL · Vendor: postgresql

Share: LinkedIn · X · Reddit

Last updated 2026-08-29 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

postgresql postgresql UPGRADE
Affected: >= 17.0 and < 17.11 · >= 18.0 and < 18.5
Fixed in: 17.11, 18.5
Safe to downgrade to: a release before 17.0
1. Check installed version
apt-cache policy postgresql || rpm -q postgresql || postgresql --version
2. UPGRADE to 17.11 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade postgresql
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade postgresql
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 17.0 (Debian / Ubuntu)
apt-cache madison postgresql sudo apt install postgresql=<VERSION_BEFORE_17.0> sudo apt-mark hold postgresql
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list postgresql sudo dnf downgrade postgresql-<VERSION_BEFORE_17.0> sudo dnf versionlock add postgresql
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-14681?

postgresql: upgrade to 17.11, 18.5. Exact commands for each OS are on this page.

Is CVE-2026-14681 being exploited?

CVE-2026-14681 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-14681 affect?

CVE-2026-14681 affects postgresql. Severity is medium (CVSS 4.2). 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

How urgent is CVE-2026-14681?

Priority 15/100. No elevated risk signals yet.

Software pages

PostgreSQL vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.