PostgreSQL discloses MD5-hashed passwords via covert timing channel
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.55% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: n/a PostgreSQL 14.23, 15.18, 16.14.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to n/a PostgreSQL 14.23, 15.18, 16.14 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover user credentials sufficient to authenticate. This does not affect scram-sha-256 passwords, the default in all supported releases. However, current databases may have MD5-hashed passwords originating in upgrades from PostgreSQL 13 or earlier. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.
- BDU:2026-07097
- ALSA-2026:26181
- ALSA-2026:26203
- ALSA-2026:26204
- ALSA-2026:27738
- ALSA-2026:27741
- ALSA-2026:27742
- ALSA-2026:27743
- ALSA-2026:28037
- ALSA-2026:28143
- ALSA-2026:28208
- ALSA-2026:28999
- openSUSE-SU-2026:10806-1
- openSUSE-SU-2026:10807-1
- openSUSE-SU-2026:10808-1
- openSUSE-SU-2026:10809-1
- openSUSE-SU-2026:10828-1
- openSUSE-SU-2026:20970-1
- openSUSE-SU-2026:21102-1
- openSUSE-SU-2026:21103-1
- Published
- May 14, 2026
- Updated
- Aug 25, 2026
- EPSS
- 0.6% · 45th percentile
- CWE
- CWE-385
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · PostgreSQL
- 6.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| postgresql | postgresql | cpe:2.3:a:postgresql:postgresql |
Using postgresql? Add it to your stack and be the first to know about CVEs like this one. (PostgreSQL)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- postgresql postgresqlbefore 14.23
- postgresql postgresql15.0 and later · before 15.18
- postgresql postgresql16.0 and later · before 16.14
- postgresql postgresql17.0 and later · before 17.10
- postgresql postgresql18.0 and later · before 18.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (PostgreSQL). Independent of NVD's CPE analysis and usually ahead of it.
n/a PostgreSQL
- 18 and later · before 18.4affected · rpm
- 17 and later · before 17.10affected · rpm
- 16 and later · before 16.14affected · rpm
- 15 and later · before 15.18affected · rpm
- before 14.23affected · rpm
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | postgresql | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql-contrib | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql-docs | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql-plperl | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql-plpython3 | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql-pltcl | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql-private-devel | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql-private-libs | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql-server | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql-server-devel | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql-static | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql-test | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql-test-rpm-macros | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql-upgrade | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql-upgrade-devel | before 16.14-1.el10_2 | 16.14-1.el10_2 |
| AlmaLinux:10 | postgresql18 | before 18.4-1.el10_2 | 18.4-1.el10_2 |
| AlmaLinux:10 | postgresql18-contrib | before 18.4-1.el10_2 | 18.4-1.el10_2 |
| AlmaLinux:10 | postgresql18-docs | before 18.4-1.el10_2 | 18.4-1.el10_2 |
| AlmaLinux:10 | postgresql18-plperl | before 18.4-1.el10_2 | 18.4-1.el10_2 |
| AlmaLinux:10 | postgresql18-plpython3 | before 18.4-1.el10_2 | 18.4-1.el10_2 |
| AlmaLinux:10 | postgresql18-private-devel | before 18.4-1.el10_2 | 18.4-1.el10_2 |
| AlmaLinux:10 | postgresql18-private-libs | before 18.4-1.el10_2 | 18.4-1.el10_2 |
| AlmaLinux:10 | postgresql18-server | before 18.4-1.el10_2 | 18.4-1.el10_2 |
| AlmaLinux:10 | postgresql18-server-devel | before 18.4-1.el10_2 | 18.4-1.el10_2 |
+96
Same product
postgresql: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-7546PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to incorrect authentication flaw allowing remote attackers57Plan
- CVE-2019-9193In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_server_program' group to 55Plan
- CVE-2020-25695A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24.49Plan
- CVE-2007-3280The Database Link library (dblink) in PostgreSQL 8.1 implements functions via CREATE statements that map to arbitrary libraries based on the44Plan
- CVE-2013-1899Argument injection vulnerability in PostgreSQL 9.2.x before 9.2.4, 9.1.x before 9.1.9, and 9.0.x before 9.0.13 allows remote attackers to ca42Plan
- CVE-2018-16850postgresql before versions 11.1, 10.6 is vulnerable to a to SQL injection in pg_upgrade and pg_dump via CREATE TRIGGER ...41Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| n/a PostgreSQL | 14.23 | Vendor (CNA) |
| n/a PostgreSQL | 15.18 | Vendor (CNA) |
| n/a PostgreSQL | 16.14 | Vendor (CNA) |
| n/a PostgreSQL | 17.10 | Vendor (CNA) |
| n/a PostgreSQL | 18.4 | Vendor (CNA) |
| almalinux:pg_repack | 1.4.8-1.module_el8.9.0+3706+885c732e · AlmaLinux:8 | Package registry (OSV) |
| almalinux:pgaudit | 1.7.0-1.module_el8.9.0+3706+885c732e · AlmaLinux:8 | Package registry (OSV) |
| almalinux:postgres-decoderbufs | 1.9.7-1.Final.module_el8.9.0+3706+885c732e · AlmaLinux:8 | Package registry (OSV) |
| almalinux:postgresql | 15.18-1.module_el8.10.0+4195+4569d728 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:postgresql-contrib | 15.18-1.module_el8.10.0+4195+4569d728 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:postgresql-docs | 15.18-1.module_el8.10.0+4195+4569d728 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:postgresql-plperl | 15.18-1.module_el8.10.0+4195+4569d728 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:postgresql-plpython3 | 15.18-1.module_el8.10.0+4195+4569d728 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:postgresql-pltcl | 15.18-1.module_el8.10.0+4195+4569d728 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:postgresql-private-devel | 15.18-1.module_el8.10.0+4195+4569d728 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:postgresql-private-libs | 15.18-1.module_el8.10.0+4195+4569d728 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:postgresql-server | 15.18-1.module_el8.10.0+4195+4569d728 · AlmaLinux:8 | Package registry (OSV) |
| alpine:postgresql15 | 15.18-r0 · Alpine:v3.20 | Package registry (OSV) |
| alpine:postgresql16 | 16.14-r0 · Alpine:v3.20 | Package registry (OSV) |
| alpine:postgresql17 | 17.10-r0 · Alpine:v3.21 | Package registry (OSV) |
| alpine:postgresql18 | 18.4-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:postgresql-15 | 15.18-0+deb12u1 · Debian:12 | Package registry (OSV) |
| debian:postgresql-17 | 17.10-0+deb13u1 · Debian:13 | Package registry (OSV) |
| debian:postgresql-18 | 18.4-1 · Debian:14 | Package registry (OSV) |
| opensuse:postgresql14 | 14.23-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql15 | 15.18-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql16 | 16.14-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql17 | 17.10-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql18 | 18.4-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:pg_repack | 0:1.4.8-1.module+el8.9.0+19797+c4ce5969 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
+36
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0254 · May 15, 2026(PostgreSQL Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-385 · Covert Timing ChannelCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- access.redhat.com/errata/RHSA-2026:21182
- access.redhat.com/errata/RHSA-2026:22878
- access.redhat.com/errata/RHSA-2026:26181
- access.redhat.com/errata/RHSA-2026:26203
- access.redhat.com/errata/RHSA-2026:26204
- access.redhat.com/errata/RHSA-2026:26524
- access.redhat.com/errata/RHSA-2026:26525
- access.redhat.com/errata/RHSA-2026:26561
- access.redhat.com/errata/RHSA-2026:27718
- access.redhat.com/errata/RHSA-2026:27738
- access.redhat.com/errata/RHSA-2026:27741
- access.redhat.com/errata/RHSA-2026:27742
- access.redhat.com/errata/RHSA-2026:27743
- access.redhat.com/errata/RHSA-2026:28037
- access.redhat.com/errata/RHSA-2026:28143
- access.redhat.com/errata/RHSA-2026:28208
- access.redhat.com/errata/RHSA-2026:28999
- access.redhat.com/errata/RHSA-2026:29212
- access.redhat.com/errata/RHSA-2026:29815
Vendor advisories and official records. Exploit/PoC links are deliberately left out.