CVE-2026-14668: PostgreSQL ctid type confusion in selectivity estimator discloses derivative of arbitrary read
Type confusion regarding input of PostgreSQL ctid data type selectivity estimator allows an object creator to view a calculation derived from the value of an arbitrary 4-byte span of memory, via a chosen non-ctid input. While the calculation loses precision, substantial memory value recovery appears possible. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 18.5 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 17.11 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 16.15 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 15.19 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 14.24
Event History
Frequently Asked Questions
What is the severity of CVE-2026-14668?
The severity of CVE-2026-14668 is classified as high with a CVSS score of 8.1.
How do I fix CVE-2026-14668?
To fix CVE-2026-14668, update PostgreSQL to the latest version where the vulnerability has been patched.
What type of attack does CVE-2026-14668 involve?
CVE-2026-14668 involves type confusion within the PostgreSQL ctid data type that can lead to unauthorized memory exposure.
Who is affected by CVE-2026-14668?
Any PostgreSQL user utilizing the affected versions and employing the ctid data type may be impacted by CVE-2026-14668.
What are the potential consequences of CVE-2026-14668?
The consequences of CVE-2026-14668 may include the disclosure of sensitive information from memory, which could be leveraged for further attacks.