PostgreSQL GSSAPI support · Improper Enforcement of Message Integrity
Source GCVE Database
Not known to be exploited · CVSS 4.2 Medium : upgrade to 18.6 or 17.11 when convenient.
Data as of 11 Nov 2026, 23:24 UTC
- EPSS
- 0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 18.6, 17.11, 18.5
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade PostgreSQL to 18.6 or 17.11; postgresql/postgresql to 18.5 or 17.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
Postgresqlpostgresql/postgresqlpkg:deb/postgresql/postgresqlOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, administrators should carefully review their pg_hba.conf and TLS configurations to ensure that the security posture meets organizational requirements. Monitoring vendor communications for updates is recommended.
Description
A vulnerability in PostgreSQL's GSSAPI support allows users to bypass pg_hba.conf rules by negotiating GSSAPI improperly via an initial direct TLS connection. This can result in connections using TLS encryption alone, potentially with weaker protection than intended. The issue affects PostgreSQL major versions 17 and 18, specifically versions before 18.5 and 17.11. Versions prior to 17 are not affected.