Skip to main content
CVE-2026-14672VulnerabilityPublished

PostgreSQL SCRAM authentication · Observable Response Discrepancy

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-14672· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium · fixed in 18.6 : update PostgreSQL when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 18.6, 17.11, 16.15 +1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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, 17.11 or 16.15; postgresql/postgresql to 18.5, 17.11 or 16.15.

Affected software

ProductAffectedFixed in
PostgreSQLAffected
  • >=18 <18.6
Fixed in
  • 18.6
PostgreSQLAffected
  • >=17 <17.11
Fixed in
  • 17.11
PostgreSQLAffected
  • >=16 <16.15
Fixed in
  • 16.15
Postgresqlpostgresql/postgresqlpkg:deb/postgresql/postgresqlOther threatsAffected
  • <16.15
  • <17.11
  • <18.5
Fixed in
  • 16.15
  • 17.11
  • 18.5

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, consider configuring all users to use the default scram_iterations count to prevent iteration count discrepancies from revealing user existence.

Description

A vulnerability in PostgreSQL SCRAM authentication allows an unauthenticated attacker to test whether a user exists by observing differences in the SCRAM iteration count in authentication responses. This affects PostgreSQL major versions 16 through 18, specifically versions before 16.15, 17.11, and 18.5. Versions prior to 16 are not affected.

References

Community reviews

Loading reviews…