CVE-2026-14672 is an observable response discrepancy in PostgreSQL SCRAM authentication. For an existing role whose SCRAM verifier uses a non-default scram_iterations value, the authentication challenge reveals that role-specific iteration count; a nonexistent role receives a challenge using the default iteration count. An unauthenticated remote party can compare these responses to determine whether a selected username exists. PostgreSQL 16 through 18 are affected before 16.15, 17.11, and 18.6, respectively; versions before PostgreSQL 16 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.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A network-accessible PostgreSQL vulnerability that requires no privileges or user interaction and can result in low-impact confidentiality disclosure. The provided content does not specify the underlying flaw mechanism.
A PostgreSQL authentication side-channel that can reveal whether a user exists when non-default scram_iterations are configured.
A PostgreSQL authentication-information disclosure issue that enables a user-existence oracle when non-default SCRAM iteration settings are used.
A PostgreSQL authentication information-disclosure flaw where response differences under non-default scram_iterations reveal whether users exist.
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.