Loading vulnerability…
CVE-2026-14681 is a protection-mechanism enforcement flaw in PostgreSQL GSSAPI support. When a client initiates an initial direct TLS connection, PostgreSQL can negotiate GSSAPI contrary to the intended pg_hba.conf policy. A connection that appears to require GSSAPI message integrity may consequently continue protected only by TLS if the TLS configuration is more permissive than the corresponding GSSAPI policy. PostgreSQL 17 before 17.11 and PostgreSQL 18 before 18.6 are affected; versions before PostgreSQL 17 are unaffected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A PostgreSQL flaw involving improper enforcement of GSSAPI encryption in SSL-coupled configurations.
A PostgreSQL 17 and 18 security-bypass vulnerability in GSSAPI message-integrity enforcement. An attacker/user can negotiate GSSAPI through an initial direct TLS connection in a way that bypasses apparent pg_hba.conf GSSAPI requirements, potentially downgrading the connection to TLS-only protection when TLS policy is weaker than GSS policy.
A PostgreSQL transport-protection flaw involving improper GSSAPI encryption enforcement when SSL is also used.
PostgreSQL GSSAPI authentication-protection bypass that can reduce required GSSAPI protections to TLS-only protection.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.