PostgreSQL up to 18.3 covert timing channel

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.0$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in PostgreSQL up to 14.22/15.17/16.13/17.9/18.3. The affected element is an unknown function. The manipulation leads to covert timing channel. This vulnerability is referenced as CVE-2026-6478. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in PostgreSQL up to 14.22/15.17/16.13/17.9/18.3 and classified as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a covert timing channel vulnerability. Using CWE to declare the problem leads to CWE-385. Covert timing channels convey information by modulating some aspect of system behavior over time, so that the program receiving the information can observe system behavior and infer protected information. Impacted is confidentiality. The summary by CVE is:

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.

It is possible to read the advisory at postgresql.org. The identification of this vulnerability is CVE-2026-6478 since 04/17/2026. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 315292 (SUSE SLES12 Security Update : postgresql18 (SUSE-SU-2026:1946-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 14.23, 15.18, 16.14, 17.10 or 18.4 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (315292) and CERT Bund (WID-SEC-2026-1544). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Open Source PostgreSQL
  • IBM QRadar SIEM

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.1
VulDB Meta Temp Score: 5.0

VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 6.5
CNA Vector (PostgreSQL): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Covert timing channel
CWE: CWE-385
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 315292
Nessus Name: SUSE SLES12 Security Update : postgresql18 (SUSE-SU-2026:1946-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: PostgreSQL 14.23/15.18/16.14/17.10/18.4

Timelineinfo

04/17/2026 CVE reserved
05/14/2026 +27 days Advisory disclosed
05/14/2026 +0 days VulDB entry created
06/25/2026 +42 days VulDB entry last update

Sourcesinfo

Product: postgresql.org

Advisory: postgresql.org
Status: Confirmed

CVE: CVE-2026-6478 (🔒)
GCVE (CVE): GCVE-0-2026-6478
GCVE (VulDB): GCVE-100-363875
CERT Bund: WID-SEC-2026-1544 - PostgreSQL: Mehrere Schwachstellen

Entryinfo

Created: 05/14/2026 15:49
Updated: 06/25/2026 20:06
Changes: 05/14/2026 15:49 (63), 05/16/2026 00:14 (7), 05/19/2026 15:19 (2), 05/28/2026 10:16 (1), 06/15/2026 15:33 (1), 06/25/2026 20:06 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!