CVE-2026-14672

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-08-13. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

Observable response discrepancy in PostgreSQL SCRAM authentication allows an unauthenticated user to test the existence of a user via observing the SCRAM iteration count. This requires the probed user to have a non-default scram_iterations count, because the authentication challenge for a nonexistent user reports the default scram_iterations. Within major versions 16-18, minor versions before PostgreSQL 18.6, 17.11, and 16.15 are affected. Versions before PostgreSQL 16 are unaffected.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 29, 2026

Advisory Details (1)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

PostgreSQL: CVE-2026-14672: PostgreSQL observable response discrepancy with non-default scram_iterations provides user existence oracle

https://www.postgresql.org/support/security/CVE-2026-14672/

Vendor Advisories for CVE-2026-14672(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-18 (18.6-0ubuntu0.26.04.1) @ resolute2026-09-19ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(10 across 6 ecosystems)
Alpine:v3.21(2)
PackageVulnerable rangeFixed inDependents
postgresql16—16.15-r0—
postgresql17—17.11-r0—
Alpine:v3.22(2)
PackageVulnerable rangeFixed inDependents
postgresql16—16.15-r0—
postgresql17—17.11-r0—
Alpine:v3.23(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.11-r0—
postgresql18—18.5-r0—
Alpine:v3.24(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.11-r0—
postgresql18—18.5-r0—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
postgresql-1717.10-0+deb13u1 ... 17.9-0+deb13u1 (7 versions)17.11-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
postgresql-1818.0-1 ... 18~~devel.20250502-1 (20 versions)18.6-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 23× in last 7d / 107× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 128 total refreshes for this CVE.

  1. 2026-09-19 02:36 UTCEG score recompute
  2. 2026-09-19 02:36 UTCVendor advisory
  3. 2026-09-19 02:36 UTCGHSA enrichment
  4. 2026-09-18 19:27 UTCEPSS rescore
  5. 2026-09-18 01:23 UTCEG score recompute
  6. 2026-09-18 01:23 UTCVendor advisory
  7. 2026-09-18 01:23 UTCGHSA enrichment
  8. 2026-09-17 00:12 UTCEG score recompute
  9. 2026-09-17 00:12 UTCVendor advisory
  10. 2026-09-17 00:11 UTCGHSA enrichment
  11. 2026-09-16 14:07 UTCEPSS rescore
  12. 2026-09-16 05:14 UTCEPSS rescore
  13. 2026-09-15 13:05 UTCEG score recompute
  14. 2026-09-15 13:05 UTCVendor advisory
  15. 2026-09-15 13:05 UTCGHSA enrichment
  16. 2026-09-14 11:05 UTCEG score recompute
  17. 2026-09-14 11:05 UTCVendor advisory
  18. 2026-09-14 11:05 UTCGHSA enrichment
  19. 2026-09-13 16:46 UTCEPSS rescore
  20. 2026-09-13 09:54 UTCEG score recompute
  21. 2026-09-13 09:54 UTCVendor advisory
  22. 2026-09-13 09:53 UTCGHSA enrichment
  23. 2026-09-12 15:00 UTCEPSS rescore
  24. 2026-09-12 08:42 UTCEG score recompute
  25. 2026-09-12 08:42 UTCVendor advisory
Show 75 more
  1. 2026-09-12 08:42 UTCGHSA enrichment
  2. 2026-09-11 14:52 UTCEPSS rescore
  3. 2026-09-11 09:36 UTCEPSS rescore
  4. 2026-09-11 07:30 UTCEG score recompute
  5. 2026-09-11 07:30 UTCVendor advisory
  6. 2026-09-11 07:30 UTCGHSA enrichment
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-10 06:18 UTCVendor advisory
  9. 2026-09-10 06:18 UTCGHSA enrichment
  10. 2026-09-09 05:06 UTCEG score recompute
  11. 2026-09-09 05:06 UTCVendor advisory
  12. 2026-09-09 05:06 UTCGHSA enrichment
  13. 2026-09-08 22:00 UTCEPSS rescore
  14. 2026-09-07 16:37 UTCEG score recompute
  15. 2026-09-07 16:37 UTCVendor advisory
  16. 2026-09-07 16:37 UTCGHSA enrichment
  17. 2026-09-07 16:01 UTCEPSS rescore
  18. 2026-09-06 13:47 UTCEPSS rescore
  19. 2026-09-06 10:15 UTCEG score recompute
  20. 2026-09-06 10:15 UTCVendor advisory
  21. 2026-09-06 10:15 UTCGHSA enrichment
  22. 2026-09-05 09:04 UTCEG score recompute
  23. 2026-09-05 09:04 UTCVendor advisory
  24. 2026-09-05 09:04 UTCGHSA enrichment
  25. 2026-09-04 07:52 UTCVendor advisory
  26. 2026-09-04 07:52 UTCGHSA enrichment
  27. 2026-09-03 05:55 UTCEG score recompute
  28. 2026-09-03 05:55 UTCVendor advisory
  29. 2026-09-03 05:54 UTCGHSA enrichment
  30. 2026-09-02 14:11 UTCEPSS rescore
  31. 2026-09-02 03:51 UTCEG score recompute
  32. 2026-09-02 03:51 UTCVendor advisory
  33. 2026-09-02 03:50 UTCGHSA enrichment
  34. 2026-09-01 13:53 UTCEPSS rescore
  35. 2026-09-01 04:39 UTCEPSS rescore
  36. 2026-09-01 01:58 UTCVendor advisory
  37. 2026-09-01 01:58 UTCGHSA enrichment
  38. 2026-08-31 00:38 UTCEG score recompute
  39. 2026-08-31 00:38 UTCVendor advisory
  40. 2026-08-31 00:38 UTCGHSA enrichment
  41. 2026-08-30 19:17 UTCEPSS rescore
  42. 2026-08-30 01:22 UTCEPSS rescore
  43. 2026-08-29 23:26 UTCEG score recompute
  44. 2026-08-29 23:26 UTCVendor advisory
  45. 2026-08-29 23:26 UTCGHSA enrichment
  46. 2026-08-29 23:14 UTCEG score recompute
  47. 2026-08-29 23:14 UTCVendor advisory
  48. 2026-08-29 23:14 UTCGHSA enrichment
  49. 2026-08-29 08:18 UTCEG score recompute
  50. 2026-08-29 08:18 UTCVendor advisory
  51. 2026-08-29 08:17 UTCGHSA enrichment
  52. 2026-08-28 21:41 UTCEPSS rescore
  53. 2026-08-28 00:50 UTCEG score recompute
  54. 2026-08-28 00:50 UTCVendor advisory
  55. 2026-08-28 00:50 UTCGHSA enrichment
  56. 2026-08-27 14:25 UTCEPSS rescore
  57. 2026-08-26 23:28 UTCEG score recompute
  58. 2026-08-26 23:28 UTCVendor advisory
  59. 2026-08-26 23:28 UTCGHSA enrichment
  60. 2026-08-26 14:46 UTCEPSS rescore
  61. 2026-08-25 22:15 UTCEG score recompute
  62. 2026-08-25 22:15 UTCVendor advisory
  63. 2026-08-25 22:15 UTCGHSA enrichment
  64. 2026-08-25 13:48 UTCEPSS rescore
  65. 2026-08-24 21:04 UTCEG score recompute
  66. 2026-08-24 21:04 UTCVendor advisory
  67. 2026-08-24 21:04 UTCGHSA enrichment
  68. 2026-08-23 19:52 UTCEG score recompute
  69. 2026-08-23 19:52 UTCVendor advisory
  70. 2026-08-23 19:52 UTCGHSA enrichment
  71. 2026-08-23 00:19 UTCEPSS rescore
  72. 2026-08-22 18:40 UTCEG score recompute
  73. 2026-08-22 18:40 UTCVendor advisory
  74. 2026-08-22 18:40 UTCGHSA enrichment
  75. 2026-08-21 23:49 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-14672?
CVE-2026-14672 is a medium vulnerability published on August 13, 2026. Observable response discrepancy in PostgreSQL SCRAM authentication allows an unauthenticated user to test the existence of a user via observing the SCRAM iteration count. This requires the probed user to have a non-default scramiterations count, because the authentication challenge for a…
When was CVE-2026-14672 disclosed?
CVE-2026-14672 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14672 actively exploited?
CVE-2026-14672 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.0% of all scored CVEs.
What is the CVSS score of CVE-2026-14672?
CVE-2026-14672 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-14672?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14672, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-14672

Explore →

Is Your Infrastructure Affected by CVE-2026-14672?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs