PostgreSQL observable response discrepancy with non-default scram_iterations provides user existence oracle (CVE-2026-14672)
A vulnerability in PostgreSQL's SCRAM authentication mechanism allows an unauthenticated attacker to determine if a user exists by observing differences in the SCRAM iteration count in authentication responses. This issue affects PostgreSQL major versions 16 through 18, specifically versions before 16.15, 17.11, and 18.5. Versions prior to 16 are not affected. The vulnerability arises because the authentication challenge for nonexistent users always reports the default iteration count, while users with non-default scram_iterations reveal a different count, enabling a user existence oracle.
AI Analysis
Technical Summary
CVE-2026-14672 is an authentication oracle vulnerability in PostgreSQL's SCRAM authentication. It allows unauthenticated attackers to test for the existence of a database user by observing the SCRAM iteration count in the authentication challenge response. The vulnerability requires the probed user to have a non-default scram_iterations setting, as nonexistent users receive a challenge with the default iteration count. This discrepancy in responses enables user enumeration. The issue affects PostgreSQL major versions 16, 17, and 18 before the minor versions 16.15, 17.11, and 18.5 respectively. Versions before 16 are unaffected. A patch is available to address this issue.
Potential Impact
An unauthenticated attacker can confirm the existence of specific database users by exploiting differences in SCRAM iteration counts during authentication challenges. This user enumeration can aid in further targeted attacks or reconnaissance but does not directly allow authentication bypass or data access.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade PostgreSQL to versions 16.15 or later, 17.11 or later, and 18.5 or later to remediate this issue. No additional mitigation is required if these updates are applied.
PostgreSQL observable response discrepancy with non-default scram_iterations provides user existence oracle (CVE-2026-14672)
Description
A vulnerability in PostgreSQL's SCRAM authentication mechanism allows an unauthenticated attacker to determine if a user exists by observing differences in the SCRAM iteration count in authentication responses. This issue affects PostgreSQL major versions 16 through 18, specifically versions before 16.15, 17.11, and 18.5. Versions prior to 16 are not affected. The vulnerability arises because the authentication challenge for nonexistent users always reports the default iteration count, while users with non-default scram_iterations reveal a different count, enabling a user existence oracle.
Affected software
pkg:deb/postgresql/postgresqlRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-14672 is an authentication oracle vulnerability in PostgreSQL's SCRAM authentication. It allows unauthenticated attackers to test for the existence of a database user by observing the SCRAM iteration count in the authentication challenge response. The vulnerability requires the probed user to have a non-default scram_iterations setting, as nonexistent users receive a challenge with the default iteration count. This discrepancy in responses enables user enumeration. The issue affects PostgreSQL major versions 16, 17, and 18 before the minor versions 16.15, 17.11, and 18.5 respectively. Versions before 16 are unaffected. A patch is available to address this issue.
Potential Impact
An unauthenticated attacker can confirm the existence of specific database users by exploiting differences in SCRAM iteration counts during authentication challenges. This user enumeration can aid in further targeted attacks or reconnaissance but does not directly allow authentication bypass or data access.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade PostgreSQL to versions 16.15 or later, 17.11 or later, and 18.5 or later to remediate this issue. No additional mitigation is required if these updates are applied.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-hp2m-55fj-8mw5
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-14672"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a7e0367bf8831d5398f874c
Added to database: 08/13/2026, 17:48:23 UTC
Last enriched: 09/08/2026, 15:15:17 UTC
Last updated: 09/28/2026, 20:25:49 UTC
Views: 54
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.