PostgreSQL up to 18.3 integer overflow

Summaryinfo

A vulnerability identified as critical has been detected in PostgreSQL up to 14.22/15.17/16.13/17.9/18.3. Affected by this vulnerability is an unknown functionality. The manipulation leads to integer overflow. This vulnerability is traded as CVE-2026-6473. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in PostgreSQL up to 14.22/15.17/16.13/17.9/18.3. It has been rated as critical. This issue affects some unknown functionality. The manipulation with an unknown input leads to a integer overflow vulnerability. Using CWE to declare the problem leads to CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Integer wraparound in multiple PostgreSQL server features allows an unprivileged database user to cause the server to undersize an allocation and write out-of-bounds. This may execute arbitrary code as the operating system user running the database. In applications that pass gigabyte-scale user inputs to the relevant database functions, the application input provider may achieve a segmentation fault. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

The advisory is shared at postgresql.org. The identification of this vulnerability is CVE-2026-6473 since 04/17/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are 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). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Debian Linux
• Ubuntu Linux
• SUSE Linux
• SUSE openSUSE
• Open Source PostgreSQL

Productinfo

Type

• Database Software

Name

• PostgreSQL

Version

• 14.0
• 14.1
• 14.2
• 14.3
• 14.4
• 14.5
• 14.6
• 14.7
• 14.8
• 14.9
• 14.10
• 14.11
• 14.12
• 14.13
• 14.14
• 14.15
• 14.16
• 14.17
• 14.18
• 14.19
• 14.20
• 14.21
• 14.22
• 15.0
• 15.1
• 15.2
• 15.3
• 15.4
• 15.5
• 15.6
• 15.7
• 15.8
• 15.9
• 15.10
• 15.11
• 15.12
• 15.13
• 15.14
• 15.15
• 15.16
• 15.17
• 16.0
• 16.1
• 16.2
• 16.3
• 16.4
• 16.5
• 16.6
• 16.7
• 16.8
• 16.9
• 16.10
• 16.11
• 16.12
• 16.13
• 17.0
• 17.1
• 17.2
• 17.3
• 17.4
• 17.5
• 17.6
• 17.7
• 17.8
• 17.9
• 18.0
• 18.1
• 18.2
• 18.3

License

• open-source

Website

• Product: https://www.postgresql.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion