REDHAT-BUG-2515322: High severity PostgreSQL postgresql vulnerability

Q: What level of access does an attacker need to exploit this issue?

The attacker must be able to create an object in a database that uses the refint module. Successful exploitation allows arbitrary code execution as the operating system user running PostgreSQL.

Q: Which PostgreSQL releases need to be remediated?

PostgreSQL versions before 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. Upgrade to the applicable fixed release or a later release.

Q: Is there a CVE identifier for this issue?

No CVE number is identified for this issue. The upstream fix was committed with the subject "refint: Remove plan cache."

Q: How can I determine whether my deployment is exposed?

Check whether the PostgreSQL version is earlier than the fixed release for its major version and whether the refint module is in use. Exposure requires an actor who can create a relevant database object.

Published Aug 13, 2026

Updated

Type confusion in PostgreSQL module "refint" allows an object creator to execute arbitrary code as the operating system user running the database. The fix for this emerged as a non-security bug report, and the fix appear in the git repository with subject "refint: Remove plan cache.", without a CVE number. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.

Affected Software

1 affected component

PostgreSQL postgresql<18.5, <17.11, <16.15, <15.19, <14.24

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade PostgreSQL to a version that resolves this vulnerability.
Fixed in 18.5
Upgrade
Upgrade PostgreSQL to a version that resolves this vulnerability.
Fixed in 17.11
Upgrade
Upgrade PostgreSQL to a version that resolves this vulnerability.
Fixed in 16.15
Upgrade
Upgrade PostgreSQL to a version that resolves this vulnerability.
Fixed in 15.19
Upgrade
Upgrade PostgreSQL to a version that resolves this vulnerability.
Fixed in 14.24

Event History

Aug 13, 2026

Data Sourced

via Red Hat·01:30 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

What level of access does an attacker need to exploit this issue?

The attacker must be able to create an object in a database that uses the refint module. Successful exploitation allows arbitrary code execution as the operating system user running PostgreSQL.

Which PostgreSQL releases need to be remediated?

PostgreSQL versions before 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. Upgrade to the applicable fixed release or a later release.

Is there a CVE identifier for this issue?

No CVE number is identified for this issue. The upstream fix was committed with the subject "refint: Remove plan cache."

How can I determine whether my deployment is exposed?

Check whether the PostgreSQL version is earlier than the fixed release for its major version and whether the refint module is in use. Exposure requires an actor who can create a relevant database object.

REDHAT-BUG-2515322: High severity PostgreSQL postgresql vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

What level of access does an attacker need to exploit this issue?

Which PostgreSQL releases need to be remediated?

Is there a CVE identifier for this issue?

How can I determine whether my deployment is exposed?

Company

Resources

Contact

Frequently Asked Questions

What level of access does an attacker need to exploit this issue?

Which PostgreSQL releases need to be remediated?

Is there a CVE identifier for this issue?

How can I determine whether my deployment is exposed?